← previous blocknext block →recent activity
Analyzing
Block #106,224,461
35 transactions · 35 stateful · 2026-09-19 16:26:44 UTC
Parallelism
51/100
Blocked
63%
Avg conflicts / tx
3.69
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,224,461 · 35 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
1w02w03w14w210w311w414w515w620w721w822w923w1024w1126w1227w1328w1429w1530w1633w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fadeba0…ef9e
0x34b655…2a6f
20 touches
45 conflicts
0x638cd0f2…cb93
0x34b655…2a6f
18 touches
36 conflicts
0xc737ce4f…a8d8
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x289d1d70…7b29
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
12 touches
15 conflicts
0x8f13071b…959c
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
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
45 conflicts on slot 0x0fadeba068…f9ef9e
Audit this contract →
← previous block·next block →recent activity