← previous blocknext block →recent activity
Analyzing
Block #106,934,900
41 transactions · 34 stateful · 2026-09-22 04:03:23 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
3.07
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,934,900 · 41 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w39w410w512w613w714w821w922w225w1026w1127w1228w1329w1434w135w1439w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
30 touches
105 conflicts
0x3e9bccd1…9cc9
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
12 touches
15 conflicts
0x24c5620c…7ac5
0x34b655…2a6f
12 touches
15 conflicts
0x56755b2b…8d44
0x34b655…2a6f
12 touches
15 conflicts
0x84fe76b9…bd24
0x37db7f…ec7b
12 touches
15 conflicts
0xaf59c69d…c904
0x37db7f…ec7b
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
105 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity