← previous blocknext block →recent activity
Analyzing
Block #106,800,962
15 transactions · 12 stateful · 2026-09-21 16:49:14 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,800,962 · 15 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
2w03w04w15w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37f16dae…7f6a
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
0x34b655…2a6f
4 touches
1 conflict
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7aa95aa1…edb2
0x065c9d…c394
2 touches
0 conflicts
0xac66dee6…a835
0x065c9d…c394
2 touches
0 conflicts
0xdfa159d0…1576
0x065c9d…c394
2 touches
0 conflicts
0xf037d42d…0c84
0x065c9d…c394
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 0x37f16dae13…be7f6a
Audit this contract →
← previous block·next block →recent activity