← previous blocknext block →recent activity
Analyzing
Block #106,366,944
30 transactions · 29 stateful · 2026-09-20 04:23:49 UTC
Parallelism
43/100
Blocked
66%
Avg conflicts / tx
4.57
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,366,944 · 30 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w310w411w513w614w715w816w917w1022w1023w1124w1225w1326w1427w1528w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55a7c54b…bdcc
0x34b655…2a6f
30 touches
105 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
20 touches
45 conflicts
0x465cbec0…6256
0x34b655…2a6f
18 touches
36 conflicts
0x4118bd12…924a
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
10 touches
10 conflicts
0x2c2761c0…476e
0x34b655…2a6f
10 touches
10 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
105 conflicts on slot 0x55a7c54b6f…4fbdcc
Audit this contract →
← previous block·next block →recent activity