← previous blocknext block →recent activity
Analyzing
Block #86,243,933
15 transactions · 13 stateful · 2026-07-07 18:13:03 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,243,933 · 15 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
1w06w17w09w110w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x077d58c3…8ed7
0x34b655…2a6f
6 touches
3 conflicts
0x1bee5aea…5f61
0x34b655…2a6f
6 touches
3 conflicts
0x02e673f3…9771
0x34b655…2a6f
6 touches
3 conflicts
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x7d05bf69…2e73
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
0x34b655…2a6f
4 touches
1 conflict
0x9fd37234…2731
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
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 0x077d58c3dc…178ed7
Audit this contract →
← previous block·next block →recent activity