← previous blocknext block →recent activity
Analyzing
Block #106,362,393
29 transactions · 28 stateful · 2026-09-20 04:00:55 UTC
Parallelism
55/100
Blocked
57%
Avg conflicts / tx
2.9
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,362,393 · 29 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w28w19w317w418w519w620w721w822w923w1024w1125w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd9ba26b…108d
0x34b655…2a6f
24 touches
66 conflicts
0x1c549b52…80c6
0x34b655…2a6f
16 touches
28 conflicts
0xecc4ac19…b4ac
0x34b655…2a6f
12 touches
15 conflicts
0x08137337…8610
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 conflicts
0x366e63bf…8a96
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
66 conflicts on slot 0xcd9ba26bf8…62108d
Audit this contract →
← previous block·next block →recent activity