← previous blocknext block →recent activity
Analyzing
Block #106,377,362
47 transactions · 42 stateful · 2026-09-20 05:16:15 UTC
Parallelism
66/100
Blocked
64%
Avg conflicts / tx
2.3
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,377,362 · 47 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
1w03w15w06w17w28w39w310w418w420w421w526w627w729w232w833w334w435w936w1037w1138w1243w1245w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xa98e9641…560c
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc644e46e…fcbc
0x34b655…2a6f
12 touches
15 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
12 touches
15 conflicts
0x80398c66…f3cc
0x34b655…2a6f
10 touches
10 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity