← previous blocknext block →recent activity
Analyzing
Block #105,852,025
36 transactions · 36 stateful · 2026-09-18 09:11:15 UTC
Parallelism
56/100
Blocked
67%
Avg conflicts / tx
3.31
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #105,852,025 · 36 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w07w08w19w010w111w112w213w114w215w316w417w518w619w721w922w1023w1124w1225w1326w1434w335w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55192654…91fe
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
22 touches
55 conflicts
0x1632f701…e67d
0x34b655…2a6f
18 touches
36 conflicts
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0x4abfb389…18f4
0x34b655…2a6f
12 touches
15 conflicts
0xee8237bd…46ad
0x34b655…2a6f
12 touches
15 conflicts
0x4118bd12…924a
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
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
55 conflicts on slot 0x551926541c…2e91fe
Audit this contract →
← previous block·next block →recent activity