← previous blocknext block →recent activity
Analyzing
Block #106,389,420
32 transactions · 32 stateful · 2026-09-20 06:16:56 UTC
Parallelism
66/100
Blocked
59%
Avg conflicts / tx
2.13
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,389,420 · 32 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w312w213w314w415w517w319w624w725w827w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39f86166…2fa2
0x34b655…2a6f
20 touches
45 conflicts
0xd2facdba…7a7e
0x34b655…2a6f
14 touches
21 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xe283e878…7262
0x34b655…2a6f
8 touches
6 conflicts
0x2130a548…c1de
0x34b655…2a6f
8 touches
6 conflicts
0x1e665745…8517
0x34b655…2a6f
6 touches
3 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0x7f1201d7…cd37
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
45 conflicts on slot 0x39f86166e8…4e2fa2
Audit this contract →
← previous block·next block →recent activity