← previous blocknext block →recent activity
Analyzing
Block #106,199,649
36 transactions · 36 stateful · 2026-09-19 14:21:49 UTC
Parallelism
72/100
Blocked
42%
Avg conflicts / tx
1.78
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,199,649 · 36 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
2w03w14w05w16w08w29w310w317w418w519w620w732w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xb0a4e112…f855
0x34b655…2a6f
16 touches
28 conflicts
0x696abaea…eb3d
0x34b655…2a6f
12 touches
15 conflicts
0xe098738f…9bbe
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xac4f6385…52f4
0x34b655…2a6f
8 touches
6 conflicts
0xcac065cd…e05c
0x34b655…2a6f
8 touches
6 conflicts
0xa6464996…3af9
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity