← previous blocknext block →recent activity
Analyzing
Block #106,004,446
22 transactions · 20 stateful · 2026-09-18 21:59:27 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,004,446 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w210w312w015w116w017w118w419w020w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x27826bde…1da4
0x34b655…2a6f
6 touches
3 conflicts
0x839c0c71…bada
0x34b655…2a6f
6 touches
3 conflicts
0x94dabb65…43a3
0x34b655…2a6f
6 touches
3 conflicts
0x45885570…ed97
0x34b655…2a6f
4 touches
1 conflict
0x65bd465d…9770
0x34b655…2a6f
4 touches
1 conflict
0x80b739e7…0ac5
0x34b655…2a6f
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity