← previous blocknext block →recent activity
Analyzing
Block #105,926,401
20 transactions · 19 stateful · 2026-09-18 15:26:28 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,926,401 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w09w010w111w212w313w417w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bec4a7f…2b70
0x34b655…2a6f
8 touches
6 conflicts
0x109d8a52…a7b7
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdbb571e4…6829
0x34b655…2a6f
6 touches
3 conflicts
0xc801509a…adee
0x34b655…2a6f
6 touches
3 conflicts
0x885efce3…7496
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x2bec4a7f82…c12b70
Audit this contract →
← previous block·next block →recent activity