← previous blocknext block →recent activity
Analyzing
Block #86,632,399
34 transactions · 26 stateful · 2026-07-09 13:30:10 UTC
Parallelism
71/100
Blocked
65%
Avg conflicts / tx
1.26
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,632,399 · 34 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w27w38w49w510w111w012w113w214w315w418w128w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1a6
0xb1dbf0…c0d3
8 touches
6 conflicts
0x8a35acfb…d1a7
0xb1dbf0…c0d3
8 touches
6 conflicts
0x8eb0ac6b…a73a
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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: 0x04fdeac2…f747d7
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity