← previous blocknext block →recent activity
Analyzing
Block #106,421,174
20 transactions · 18 stateful · 2026-09-20 08:56:44 UTC
Parallelism
75/100
Blocked
39%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,421,174 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w214w215w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6d040d9…9ae3
0x34b655…2a6f
8 touches
6 conflicts
0x0407c5a8…572a
0x34b655…2a6f
8 touches
6 conflicts
0x4118bd12…924a
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
8 touches
6 conflicts
0x9b1a2d0b…f2e9
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x310a7246…2dcb
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
6 conflicts on slot 0xd6d040d989…9c9ae3
Audit this contract →
← previous block·next block →recent activity