← previous blocknext block →recent activity
Analyzing
Block #86,385,773
25 transactions · 22 stateful · 2026-07-08 10:00:28 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,385,773 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w28w011w112w118w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x2bf5914f…c75d
0x34b655…2a6f
6 touches
3 conflicts
0x217a0f43…5d80
0x34b655…2a6f
5 touches
3 conflicts
0x8eb0ac6b…a73a
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