← previous blocknext block →recent activity
Analyzing
Block #106,414,838
21 transactions · 21 stateful · 2026-09-20 08:24:51 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,414,838 · 21 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
2w03w14w15w213w214w315w316w418w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72083f0d…082a
0x34b655…2a6f
8 touches
6 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x2533fe3f…344d
0x34b655…2a6f
8 touches
6 conflicts
0x31e47e6c…87f9
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x6d955786…1327
0x34b655…2a6f
8 touches
6 conflicts
0xaf717b83…4875
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 0x72083f0d9f…8e082a
Audit this contract →
← previous block·next block →recent activity