← previous blocknext block →recent activity
Analyzing
Block #86,787,678
23 transactions · 20 stateful · 2026-07-10 06:48:24 UTC
Parallelism
78/100
Blocked
20%
Avg conflicts / tx
0.35
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,787,678 · 23 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
4w05w16w29w010w011w317w018w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a6
0xb1dbf0…c0d3
6 touches
3 conflicts
0x313d3d93…4aa2
0x34b655…2a6f
4 touches
1 conflict
0x36638a70…343b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48b8d2e5…3f2f
0x34b655…2a6f
4 touches
1 conflict
0x4b8b3363…6632
0x34b655…2a6f
4 touches
1 conflict
0x4b8b3363…6633
0x34b655…2a6f
4 touches
1 conflict
0x57781422…47c1
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: 0xb1dbf05f…b1c0d3
3 conflicts on slot 0x8a35acfbc1…6bd1a6
Audit this contract →
← previous block·next block →recent activity