← previous blocknext block →recent activity
Analyzing
Block #106,568,967
14 transactions · 13 stateful · 2026-09-20 21:20:36 UTC
Parallelism
50/100
Blocked
62%
Avg conflicts / tx
1.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,568,967 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w17w28w39w410w011w512w613w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ee0b65a…6d40
0x34b655…2a6f
12 touches
15 conflicts
0xc37e3093…d769
0x34b655…2a6f
12 touches
15 conflicts
0x2aab0897…78f7
0x34b655…2a6f
6 touches
3 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x580c6fe7…0fe8
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x110a3804…f842
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0x4ee0b65a93…c56d40
Audit this contract →
← previous block·next block →recent activity