← previous blocknext block →recent activity
Analyzing
Block #87,736,071
26 transactions · 25 stateful · 2026-07-14 16:30:35 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,736,071 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w18w29w310w414w115w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8df5fa2c…02e6
0x34b655…2a6f
8 touches
6 conflicts
0x3cfe4586…0bd9
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0xd0243b19…507b
0x34b655…2a6f
6 touches
3 conflicts
0xe3f2706b…d3ec
0x34b655…2a6f
6 touches
3 conflicts
0x20317244…edb4
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x342ae6d7…2e17
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 0x8df5fa2cd3…4b02e6
Audit this contract →
← previous block·next block →recent activity