← previous blocknext block →recent activity
Analyzing
Block #105,606,542
24 transactions · 21 stateful · 2026-09-17 12:34:15 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,606,542 · 24 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
1w03w04w15w26w37w08w09w110w111w112w013w117w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ad95756…97d8
0x34b655…2a6f
8 touches
6 conflicts
0x074c08f8…fb56
0x34b655…2a6f
8 touches
6 conflicts
0xe3684e08…c96a
0x34b655…2a6f
6 touches
3 conflicts
0x953517cb…cdec
0x34b655…2a6f
6 touches
3 conflicts
0x76622fb2…4f08
0x34b655…2a6f
4 touches
1 conflict
0x879e8ac4…809d
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
6 conflicts on slot 0x4ad95756ec…3f97d8
Audit this contract →
← previous block·next block →recent activity