← previous blocknext block →recent activity
Analyzing
Block #87,715,221
19 transactions · 18 stateful · 2026-07-14 14:11:01 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,715,221 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w19w210w011w312w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x505b37d8…d3fc
0x34b655…2a6f
6 touches
3 conflicts
0x43fab434…896f
0xa6afd3…d132
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x86f32276…0ebf
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xab5ba139…ea6f
0x34b655…2a6f
4 touches
1 conflict
0xc573ca73…fcd2
0x34b655…2a6f
4 touches
1 conflict
0xe741c135…25a9
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 0x505b37d8ec…d2d3fc
Audit this contract →
← previous block·next block →recent activity