← previous blocknext block →recent activity
Analyzing
Block #86,735,325
30 transactions · 25 stateful · 2026-07-10 00:58:41 UTC
Parallelism
80/100
Blocked
60%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,735,325 · 30 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
1w02w17w28w29w010w111w212w315w016w117w118w219w321w422w527w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a8
0xb1dbf0…c0d3
10 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x8a35acfb…d1a7
0xb1dbf0…c0d3
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xc6dcef4f…39dd
0x34b655…2a6f
6 touches
3 conflicts
0xf07207b3…cefc
0xb1dbf0…c0d3
6 touches
3 conflicts
0xecd78617…967e
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
10 conflicts on slot 0x8a35acfbc1…6bd1a8
Audit this contract →
← previous block·next block →recent activity