← previous blocknext block →recent activity
Analyzing
Block #105,471,036
24 transactions · 22 stateful · 2026-09-17 01:12:17 UTC
Parallelism
75/100
Blocked
32%
Avg conflicts / tx
0.54
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,471,036 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w211w218w319w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x336e4798…520c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa5811d93…8c73
0x34b655…2a6f
6 touches
3 conflicts
0xf17c2392…228e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2a58d502…385c
0x34b655…2a6f
4 touches
1 conflict
0x6d955786…1327
0x34b655…2a6f
4 touches
1 conflict
0x9210e826…1414
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 0x336e4798d6…15520c
Audit this contract →
← previous block·next block →recent activity