← previous blocknext block →recent activity
Analyzing
Block #106,481,652
22 transactions · 19 stateful · 2026-09-20 14:01:09 UTC
Parallelism
82/100
Blocked
26%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,481,652 · 22 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
2w04w05w16w28w010w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c840894…764a
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
4 touches
1 conflict
0xdd24145c…0c0b
0x34b655…2a6f
4 touches
1 conflict
0x17dcb440…2d46
0x34b655…2a6f
4 touches
1 conflict
0xdf64e5e6…75e8
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
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 0x1c84089465…17764a
Audit this contract →
← previous block·next block →recent activity