← previous blocknext block →recent activity
Analyzing
Block #86,317,912
9 transactions · 9 stateful · 2026-07-08 02:27:03 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,317,912 · 9 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d6b9af1…9a38
0x34b655…2a6f
4 touches
1 conflict
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x03a55247…abfe
0x34b655…2a6f
2 touches
0 conflicts
0x181732de…9796
0x34b655…2a6f
2 touches
0 conflicts
0x1b40f7b0…ff37
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x28358a8e…323d
0x34b655…2a6f
2 touches
0 conflicts
0x3381dba5…8845
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 0x7d6b9af162…f89a38
Audit this contract →
← previous block·next block →recent activity