← previous blocknext block →recent activity
Analyzing
Block #87,304,764
22 transactions · 22 stateful · 2026-07-12 16:25:15 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,304,764 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w27w39w310w417w119w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37ee30c9…9e70
0x34b655…2a6f
6 touches
3 conflicts
0x9a2de05d…3e6b
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x245cdeb1…298b
0x34b655…2a6f
4 touches
1 conflict
0x253ce85e…dd84
0x34b655…2a6f
4 touches
1 conflict
0x4c214bb3…c5d3
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 0x37ee30c996…d19e70
Audit this contract →
← previous block·next block →recent activity