← previous blocknext block →recent activity
Analyzing
Block #105,600,896
17 transactions · 17 stateful · 2026-09-17 12:05:50 UTC
Parallelism
76/100
Blocked
24%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,600,896 · 17 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
1w02w04w15w212w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1282324f…2257
0x34b655…2a6f
8 touches
6 conflicts
0x5ddc4a77…765e
0x34b655…2a6f
8 touches
6 conflicts
0xf999c744…7736
0x40c49f…2af0
4 touches
1 conflict
0x0122ee8b…56f5
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe3684e08…c96a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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
6 conflicts on slot 0x1282324f3f…0c2257
Audit this contract →
← previous block·next block →recent activity