← previous blocknext block →recent activity
Analyzing
Block #105,446,011
20 transactions · 19 stateful · 2026-09-16 23:06:20 UTC
Parallelism
85/100
Blocked
37%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,446,011 · 20 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
1w02w03w14w05w16w19w111w012w114w015w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd16ffb3d…fe01
0x34b655…2a6f
6 touches
3 conflicts
0x81d11f44…69b8
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0xb179b364…82cf
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
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 0xd16ffb3db8…81fe01
Audit this contract →
← previous block·next block →recent activity