← previous blocknext block →recent activity
Analyzing
Block #106,453,424
56 transactions · 49 stateful · 2026-09-20 11:39:06 UTC
Parallelism
63/100
Blocked
80%
Avg conflicts / tx
3.39
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #106,453,424 · 56 txs across 21 waves · depth 21
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
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w07w18w29w310w411w523w325w637w342w1543w444w546w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0x94e7f277…471b
0x34b655…2a6f
12 touches
15 conflicts
0x06a7c750…5d32
0x34b655…2a6f
12 touches
15 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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity