← previous blocknext block →recent activity
Analyzing
Block #86,350,510
13 transactions · 11 stateful · 2026-07-08 06:04:41 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,350,510 · 13 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
2w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6cdad76f…2bed
0x34b655…2a6f
5 touches
3 conflicts
0x2c75ca93…a569
0x34b655…2a6f
4 touches
1 conflict
0x2f0ec586…3c98
0x34b655…2a6f
4 touches
1 conflict
0x33ecb428…8b5d
0x34b655…2a6f
4 touches
1 conflict
0x37773728…f3a4
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity