← previous blocknext block →recent activity
Analyzing
Block #86,256,462
16 transactions · 13 stateful · 2026-07-07 19:36:50 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,256,462 · 16 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
1w02w13w24w010w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0xb56f0740…7542
0x34b655…2a6f
4 touches
1 conflict
0x55b2239f…fec5
0x34b655…2a6f
4 touches
1 conflict
0x8f7fccad…c89b
0x34b655…2a6f
2 touches
0 conflicts
0xb503dcab…7c61
0x34b655…2a6f
2 touches
0 conflicts
0xdf84a78e…ba56
0x34b655…2a6f
2 touches
0 conflicts
0xec0e0220…cb90
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity