← previous blocknext block →recent activity
Analyzing
Block #106,046,348
23 transactions · 19 stateful · 2026-09-19 01:30:19 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,046,348 · 23 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
6w07w08w19w210w313w114w216w319w220w422w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x907bf02c…6fa7
0xd32edf…ff58
7 touches
6 conflicts
0xddd20e39…d524
0x34b655…2a6f
6 touches
3 conflicts
0x3f152ba8…cea6
0x34b655…2a6f
4 touches
1 conflict
0x45885570…ed97
0x34b655…2a6f
4 touches
1 conflict
0x4bc03493…4a98
0x34b655…2a6f
4 touches
1 conflict
0x68292fe7…d918
0x34b655…2a6f
4 touches
1 conflict
0x8b9390da…3820
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity