← previous blocknext block →recent activity
Analyzing
Block #106,569,450
33 transactions · 33 stateful · 2026-09-20 21:23:02 UTC
Parallelism
91/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,569,450 · 33 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
5w06w18w09w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xdddf97e5…1c90
0x34b655…2a6f
4 touches
1 conflict
0x8ffa3328…ce11
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x213ee207…a151
0x34ae4d…3fc5
2 touches
0 conflicts
0x1f00a5b3…bf76
0x34b655…2a6f
2 touches
0 conflicts
0x2e5882a6…eb1f
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity