← previous blocknext block →recent activity
Analyzing
Block #90,206,020
11 transactions · 11 stateful · 2026-07-25 12:47:31 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,206,020 · 11 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
2w05w16w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
4 touches
1 conflict
0x438268c2…c848
0x34b655…2a6f
4 touches
1 conflict
0x438268c2…c849
0x34b655…2a6f
4 touches
1 conflict
0x4e1de22c…2615
0x34b655…2a6f
4 touches
1 conflict
0x6561b826…f343
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810d
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
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity