← previous blocknext block →recent activity
Analyzing
Block #87,327,469
18 transactions · 18 stateful · 2026-07-12 18:57:06 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,327,469 · 18 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
1w02w14w05w16w27w310w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eac6378…36f4
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
6 touches
3 conflicts
0x21d22421…0b7a
0x34b655…2a6f
4 touches
1 conflict
0x2b7950c1…2342
0x34b655…2a6f
4 touches
1 conflict
0x30ded6ec…3424
0x34b655…2a6f
4 touches
1 conflict
0x3817764d…242b
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 0x0eac637818…cb36f4
Audit this contract →
← previous block·next block →recent activity