← previous blocknext block →recent activity
Analyzing
Block #106,549,311
22 transactions · 20 stateful · 2026-09-20 19:41:41 UTC
Parallelism
55/100
Blocked
50%
Avg conflicts / tx
2.05
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,549,311 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w27w09w011w314w415w516w617w718w819w921w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdc81195…034d
0x34b655…2a6f
16 touches
28 conflicts
0x07c47b1c…93c8
0x34b655…2a6f
12 touches
15 conflicts
0x3b6e959d…158f
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x67a56c8b…f955
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xcdc8119530…c3034d
Audit this contract →
← previous block·next block →recent activity