← previous blocknext block →recent activity
Analyzing
Block #86,506,344
22 transactions · 17 stateful · 2026-07-08 23:26:04 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,506,344 · 22 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
1w02w05w16w27w38w19w210w311w412w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffa7d0a4…b10a
0x40c49f…2af0
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x342fbbca…d443
0x40c49f…2af0
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x7c6a17fa…e95d
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0xb9b4eff6…c3ef
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: 0x40c49f17…d22af0
6 conflicts on slot 0xffa7d0a419…63b10a
Audit this contract →
← previous block·next block →recent activity