← previous blocknext block →recent activity
Analyzing
Block #106,924,129
34 transactions · 33 stateful · 2026-09-22 03:09:11 UTC
Parallelism
50/100
Blocked
58%
Avg conflicts / tx
2.68
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,924,129 · 34 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
2w07w08w19w210w311w412w513w614w715w816w917w1018w1119w1220w122w828w1329w1430w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf64e5e6…75e8
0x34b655…2a6f
18 touches
36 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
18 touches
36 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0x7bdc8819…040a
0x34b655…2a6f
14 touches
21 conflicts
0xd84f6e6b…e007
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x085d5985…c9cd
0x34b655…2a6f
12 touches
15 conflicts
0xea79e6d3…68ad
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
36 conflicts on slot 0xdf64e5e6b0…c975e8
Audit this contract →
← previous block·next block →recent activity