← previous blocknext block →recent activity
Analyzing
Block #106,015,309
13 transactions · 13 stateful · 2026-09-18 22:54:07 UTC
Parallelism
54/100
Blocked
46%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,015,309 · 13 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
1w02w13w26w37w410w512w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52b0bc2b…1305
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe5250927…ef6a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x30eed06e…c832
0x34b655…2a6f
6 touches
3 conflicts
0x1ea4da44…a461
0x37db7f…ec7b
6 touches
3 conflicts
0xaf59c69d…c904
0x37db7f…ec7b
6 touches
3 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
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
6 conflicts on slot 0x52b0bc2bf4…ec1305
Audit this contract →
← previous block·next block →recent activity