← previous blocknext block →recent activity
Analyzing
Block #105,857,803
20 transactions · 18 stateful · 2026-09-18 09:40:20 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,857,803 · 20 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
2w07w08w112w113w214w315w416w519w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8db32935…81a7
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x08e6e52f…3d80
0x34b655…2a6f
10 touches
10 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
10 touches
10 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x3c7806c7…9d56
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
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
10 conflicts on slot 0x8db3293548…c981a7
Audit this contract →
← previous block·next block →recent activity