← previous blocknext block →recent activity
Analyzing
Block #106,388,449
20 transactions · 19 stateful · 2026-09-20 06:12:03 UTC
Parallelism
50/100
Blocked
58%
Avg conflicts / tx
2.15
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,388,449 · 20 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
2w03w15w06w17w29w311w412w513w614w715w816w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad1d9367…3f9d
0x34b655…2a6f
16 touches
28 conflicts
0x310a7246…2dcb
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xbaf77397…e798
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
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 0xad1d936705…663f9d
Audit this contract →
← previous block·next block →recent activity