← previous blocknext block →recent activity
Analyzing
Block #106,466,812
14 transactions · 13 stateful · 2026-09-20 12:46:29 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,466,812 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w07w18w09w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xbf40879e…ca45
0xd32edf…ff58
3 touches
1 conflict
0x173b64af…6c43
0x34b655…2a6f
2 touches
0 conflicts
0x2ffcae11…8b17
0x34b655…2a6f
2 touches
0 conflicts
0x3948878d…28df
0x34b655…2a6f
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
1 conflict on slot 0x045532dd4b…244b7d
Audit this contract →
← previous block·next block →recent activity