← previous blocknext block →recent activity
Analyzing
Block #106,569,103
22 transactions · 20 stateful · 2026-09-20 21:21:17 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,569,103 · 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
3w04w06w18w29w316w017w118w419w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
4 touches
1 conflict
0x2f50c84a…3640
0x34b655…2a6f
4 touches
1 conflict
0x556beb43…e627
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0x7aa463de…e7b8
0x34b655…2a6f
4 touches
1 conflict
0x7c8cf338…6e72
0x34b655…2a6f
4 touches
1 conflict
0x97394169…cfc0
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