← previous blocknext block →recent activity
Analyzing
Block #106,336,524
15 transactions · 14 stateful · 2026-09-20 01:50:43 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,336,524 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w110w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x167de262…f61f
0x34b655…2a6f
4 touches
1 conflict
0x3352001f…4665
0x34b655…2a6f
4 touches
1 conflict
0x5aa9ecdf…e743
0x34b655…2a6f
4 touches
1 conflict
0x5ee1769f…2d59
0x34b655…2a6f
4 touches
1 conflict
0xf1fbcd40…9515
0x34ae4d…3fc5
2 touches
0 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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity