← previous blocknext block →recent activity
Analyzing
Block #86,830,389
21 transactions · 18 stateful · 2026-07-10 11:33:58 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,830,389 · 21 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
3w010w111w012w115w016w117w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
8 touches
6 conflicts
0x2697123c…8526
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x9e75f809…fbc6
0x34b655…2a6f
6 touches
3 conflicts
0x0db8e93a…7dd1
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0b34a794…400b
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity