← previous blocknext block →recent activity
Analyzing
Block #86,789,712
15 transactions · 12 stateful · 2026-07-10 07:01:56 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,789,712 · 15 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
6w07w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04c1c529…0ee1
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x79ace5b6…8d37
0x34b655…2a6f
6 touches
3 conflicts
0x5f43f2bc…e94f
0x34b655…2a6f
6 touches
3 conflicts
0x4c2e78a1…2f95
0x34b655…2a6f
6 touches
3 conflicts
0xcc13c07b…d7cc
0x34b655…2a6f
4 touches
1 conflict
0x0c15f714…46ab
0x34b655…2a6f
4 touches
1 conflict
0x19caa5cc…17c7
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
3 conflicts on slot 0x04c1c52913…7f0ee1
Audit this contract →
← previous block·next block →recent activity