← previous blocknext block →recent activity
Analyzing
Block #106,427,378
19 transactions · 16 stateful · 2026-09-20 09:27:57 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,427,378 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w213w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5060cdde…445d
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xe1944aff…428b
0x34b655…2a6f
8 touches
6 conflicts
0x0f270a31…640c
0x34b655…2a6f
8 touches
6 conflicts
0x48203298…65cb
0x34b655…2a6f
8 touches
6 conflicts
0xb07065eb…47da
0x34b655…2a6f
8 touches
6 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
8 touches
6 conflicts
0x4984f7be…d515
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 0x5060cdde9e…d4445d
Audit this contract →
← previous block·next block →recent activity