← previous blocknext block →recent activity
Analyzing
Block #87,051,837
11 transactions · 9 stateful · 2026-07-11 12:13:57 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,051,837 · 11 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
4w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdb88134d…d6c1
0x34b655…2a6f
4 touches
1 conflict
0xdb88134d…d6c2
0x34b655…2a6f
4 touches
1 conflict
0xe01cf18a…715e
0x34b655…2a6f
4 touches
1 conflict
0xe3684e08…c96a
0x34b655…2a6f
4 touches
1 conflict
0xe860e8c0…de9b
0x34b655…2a6f
4 touches
1 conflict
0x3222881e…2a41
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity