← previous blocknext block →recent activity
Analyzing
Block #86,830,962
12 transactions · 11 stateful · 2026-07-10 11:37:48 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,830,962 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcaf5a5ac…09f0
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf45f2405…c8f9
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x39cc2185…cacb
0x34b655…2a6f
4 touches
1 conflict
0x39cc2185…caca
0x34b655…2a6f
4 touches
1 conflict
0xe4636320…f407
0x34b655…2a6f
4 touches
1 conflict
0x4f08800a…2446
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
3 conflicts on slot 0xcaf5a5ac3b…8009f0
Audit this contract →
← previous block·next block →recent activity