← previous blocknext block →recent activity
Analyzing
Block #86,789,069
12 transactions · 10 stateful · 2026-07-10 06:57:40 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,789,069 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x698e3c53…a4c4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x606bc50d…4c10
0x34b655…2a6f
4 touches
1 conflict
0x555948dc…dcd1
0x065c9d…c394
2 touches
0 conflicts
0x5d7bfb87…0be4
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
0x065c9d…c394
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
3 conflicts on slot 0x698e3c537a…0da4c4
Audit this contract →
← previous block·next block →recent activity