← previous blocknext block →recent activity
Analyzing
Block #106,422,318
52 transactions · 44 stateful · 2026-09-20 09:02:29 UTC
Parallelism
73/100
Blocked
70%
Avg conflicts / tx
2.12
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,422,318 · 52 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w06w07w18w29w310w416w517w118w220w125w628w529w332w633w636w338w742w143w445w746w847w948w1049w1150w1251w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xf89f5e80…5215
0x34b655…2a6f
12 touches
15 conflicts
0xb6ed530c…d450
0x34b655…2a6f
12 touches
15 conflicts
0xc5184473…3d1a
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity