← previous blocknext block →recent activity
Analyzing
Block #86,737,620
13 transactions · 9 stateful · 2026-07-10 01:14:02 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,737,620 · 13 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ffe7d94…61ea
0x34b655…2a6f
4 touches
1 conflict
0x0bc5d643…38d8
0x34b655…2a6f
4 touches
1 conflict
0x0bc5d643…38d9
0x34b655…2a6f
4 touches
1 conflict
0xc71e6775…6ffe
0x34b655…2a6f
4 touches
1 conflict
0x0f69f34e…c78e
0x34b655…2a6f
2 touches
0 conflicts
0x1535d171…c68b
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
2 touches
0 conflicts
0xa08f40b2…9a93
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: Perpl
1 conflict on slot 0x1ffe7d94d4…6b61ea
Audit this contract →
← previous block·next block →recent activity