← previous blocknext block →recent activity
Analyzing
Block #87,057,204
13 transactions · 12 stateful · 2026-07-11 12:49:53 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,057,204 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1add9b2…ad0b
0x34b655…2a6f
4 touches
1 conflict
0xe3e5befe…fcdb
0x34b655…2a6f
4 touches
1 conflict
0xe3e5befe…fcda
0x34b655…2a6f
4 touches
1 conflict
0xdc3d4f40…12c9
0x34b655…2a6f
4 touches
1 conflict
0xd3c18929…9140
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0x013a6b08…d120
0x34b655…2a6f
4 touches
1 conflict
0x08024b2c…d265
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
1 conflict on slot 0xc1add9b223…39ad0b
Audit this contract →
← previous block·next block →recent activity