← previous blocknext block →recent activity
Analyzing
Block #106,037,709
16 transactions · 13 stateful · 2026-09-19 00:46:50 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,037,709 · 16 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
1w03w14w25w37w413w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19cb4cde…bfd9
0x34b655…2a6f
10 touches
10 conflicts
0x565a4765…ae15
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9430e759…86df
0x34b655…2a6f
6 touches
3 conflicts
0xd597209e…9800
0x34b655…2a6f
4 touches
1 conflict
0x0b32343b…3ae6
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
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 0x19cb4cde58…72bfd9
Audit this contract →
← previous block·next block →recent activity