← previous blocknext block →recent activity
Analyzing
Block #86,059,700
25 transactions · 21 stateful · 2026-07-06 21:43:13 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,059,700 · 25 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
1w02w13w05w28w09w110w313w014w116w417w020w223w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x2d59fc…cd50
10 touches
10 conflicts
0x00000000…0003
0x2d59fc…cd50
10 touches
10 conflicts
0x00000000…0004
0x2d59fc…cd50
10 touches
10 conflicts
0x3f1434d4…1ce1
0x11ed3b…2c96
10 touches
10 conflicts
0x3f1434d4…1ce1
0x3bd359…433a
10 touches
10 conflicts
0x4d658fb7…ed44
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x9aff966c…53ce
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: 0x2d59fc33…60cd50
10 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity