← previous blocknext block →recent activity
Analyzing
Block #86,489,335
21 transactions · 14 stateful · 2026-07-08 21:32:37 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,489,335 · 21 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
1w02w16w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59dccbd8…2bf6
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0xbeae13c8…1ab1
0xd32edf…ff58
3 touches
1 conflict
0x272c343e…34fb
0x065c9d…c394
2 touches
0 conflicts
0x400eda41…ef84
0x065c9d…c394
2 touches
0 conflicts
0x917970a6…0930
0x065c9d…c394
2 touches
0 conflicts
0xa047e07c…96a5
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 0x59dccbd857…c52bf6
Audit this contract →
← previous block·next block →recent activity