← previous blocknext block →recent activity
Analyzing
Block #86,710,643
10 transactions · 9 stateful · 2026-07-09 22:13:44 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,710,643 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0xb07a0849…3b62
0xb1dbf0…c0d3
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7b3b9a41…c5dd
0x1c8a33…d316
2 touches
0 conflicts
0xbba8ddee…ed78
0x1c8a33…d316
2 touches
0 conflicts
0xd8e48d70…1d28
0x1c8a33…d316
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0xc3a8e1d6…e816
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: 0xb1dbf05f…b1c0d3
1 conflict on slot 0x8a35acfbc1…6bd1a8
Audit this contract →
← previous block·next block →recent activity