← previous blocknext block →recent activity
Analyzing
Block #106,463,289
18 transactions · 14 stateful · 2026-09-20 12:28:45 UTC
Parallelism
72/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,463,289 · 18 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
1w03w04w15w29w112w213w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef948c34…0463
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xba4adf08…3e3a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x3f7a314f…946b
0x34b655…2a6f
4 touches
1 conflict
0xfdd131fa…dbdb
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xef948c34d4…960463
Audit this contract →
← previous block·next block →recent activity