← previous blocknext block →recent activity
Analyzing
Block #86,675,413
16 transactions · 12 stateful · 2026-07-09 18:18:43 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,675,413 · 16 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
3w05w06w17w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3eedc44…3740
0x34b655…2a6f
4 touches
1 conflict
0x957c875f…b3f9
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0xc3eedc44…373f
0x34b655…2a6f
4 touches
1 conflict
0x43c2fa32…4d82
0x34b655…2a6f
2 touches
0 conflicts
0x64275949…d698
0x34b655…2a6f
2 touches
0 conflicts
0x8234b445…e919
0x34b655…2a6f
2 touches
0 conflicts
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 0xc3eedc448d…c63740
Audit this contract →
← previous block·next block →recent activity