← previous blocknext block →recent activity
Analyzing
Block #86,734,998
14 transactions · 10 stateful · 2026-07-10 00:56:30 UTC
Parallelism
86/100
Blocked
10%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,734,998 · 14 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
5w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83bf1cc7…260e
0x34b655…2a6f
4 touches
1 conflict
0xa08f40b2…9a93
0x34b655…2a6f
4 touches
1 conflict
0x0bc5d643…38d9
0x34b655…2a6f
4 touches
1 conflict
0x0bc5d643…38d8
0x34b655…2a6f
4 touches
1 conflict
0x1ffe7d94…61ea
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x90615537…b456
0x34b655…2a6f
4 touches
1 conflict
0x4ebc2a88…8301
0x34b655…2a6f
3 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
1 conflict on slot 0x83bf1cc7fb…18260e
Audit this contract →
← previous block·next block →recent activity