← previous blocknext block →recent activity
Analyzing
Block #90,445,802
10 transactions · 9 stateful · 2026-07-26 09:08:55 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,445,802 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5d321d…a474
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xba5ff1c3…4ff1
0x34b655…2a6f
6 touches
3 conflicts
0xc44901fe…0fef
0x34b655…2a6f
4 touches
1 conflict
0xfd5be853…17a0
0x34b655…2a6f
4 touches
1 conflict
0x0af9b708…ae17
0x34b655…2a6f
4 touches
1 conflict
0x12659c8c…062e
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0x1a5d321d5d…0da474
Audit this contract →
← previous block·next block →recent activity