← previous blocknext block →recent activity
Analyzing
Block #86,792,234
14 transactions · 8 stateful · 2026-07-10 07:18:47 UTC
Parallelism
86/100
Blocked
13%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,792,234 · 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c3621c7…3e11
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x198bae6a…f31c
0x34b655…2a6f
2 touches
0 conflicts
0x3a1edb3e…b841
0x34b655…2a6f
2 touches
0 conflicts
0x3c190da8…2a1b
0x34b655…2a6f
2 touches
0 conflicts
0x666b28db…11f0
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 0x3c3621c729…5b3e11
Audit this contract →
← previous block·next block →recent activity