← previous blocknext block →recent activity
Analyzing
Block #105,601,037
19 transactions · 18 stateful · 2026-09-17 12:06:32 UTC
Parallelism
53/100
Blocked
44%
Avg conflicts / tx
1.89
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,601,037 · 19 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w715w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x178a61ad…4958
0x34b655…2a6f
18 touches
36 conflicts
0x13d4d00c…f4e6
0x34b655…2a6f
12 touches
15 conflicts
0x38bcfe5f…6c71
0x34b655…2a6f
10 touches
10 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
10 touches
10 conflicts
0x4ad9accf…9bca
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x2d82b7d5…cc2f
0x34b655…2a6f
8 touches
6 conflicts
0x2014e4bd…c10b
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x178a61ad8a…8c4958
Audit this contract →
← previous block·next block →recent activity