← previous blocknext block →recent activity
Analyzing
Block #106,541,194
20 transactions · 19 stateful · 2026-09-20 19:00:50 UTC
Parallelism
80/100
Blocked
26%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,541,194 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w06w18w112w214w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6442a560…698f
0x34b655…2a6f
4 touches
1 conflict
0xb14942a2…d798
0x065c9d…c394
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd2862d04…388c
0x34b655…2a6f
4 touches
1 conflict
0xea818990…b6d4
0x34b655…2a6f
4 touches
1 conflict
0xfac38cc8…fb9d
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
1 conflict on slot 0x6442a5603f…98698f
Audit this contract →
← previous block·next block →recent activity