← previous blocknext block →recent activity
Analyzing
Block #90,330,364
9 transactions · 8 stateful · 2026-07-25 23:16:37 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,330,364 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03c2acba…6f0f
0x34b655…2a6f
4 touches
1 conflict
0x624dcd74…fd58
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x85c0f85c…ea7b
0x34b655…2a6f
4 touches
1 conflict
0x03c2acba…6f0e
0x34b655…2a6f
4 touches
1 conflict
0x282f129e…8f33
0x34b655…2a6f
2 touches
0 conflicts
0x342222e8…2ec4
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x03c2acba63…fc6f0f
Audit this contract →
← previous block·next block →recent activity