← previous blocknext block →recent activity
Analyzing
Block #86,914,392
15 transactions · 13 stateful · 2026-07-10 20:55:36 UTC
Parallelism
67/100
Blocked
31%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,914,392 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w18w29w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2efac4f6…3abf
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x4f394483…ff62
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3c3621c7…3e11
0x34b655…2a6f
6 touches
3 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
4 touches
1 conflict
0x94710b77…a921
0x34b655…2a6f
4 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
10 conflicts on slot 0x2efac4f6c8…eb3abf
Audit this contract →
← previous block·next block →recent activity