← previous blocknext block →recent activity
Analyzing
Block #86,804,107
18 transactions · 14 stateful · 2026-07-10 08:38:07 UTC
Parallelism
83/100
Blocked
21%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,804,107 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w09w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf5e934d…7ef6
0x34b655…2a6f
4 touches
1 conflict
0x5f43f2bc…e94f
0x34b655…2a6f
4 touches
1 conflict
0x7985b1c9…9c1d
0x34b655…2a6f
4 touches
1 conflict
0x7985b1c9…9c1e
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc300a507…2a8b
0xa6afd3…d132
3 touches
1 conflict
0x5f410dcf…79ee
0x34b655…2a6f
3 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
1 conflict on slot 0xaf5e934de9…617ef6
Audit this contract →
← previous block·next block →recent activity