← previous blocknext block →recent activity
Analyzing
Block #106,950,834
24 transactions · 21 stateful · 2026-09-22 05:23:36 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,950,834 · 24 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
2w03w14w25w06w18w09w111w212w315w317w418w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e0846cb…3067
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xa9a9d0e0…4087
0x34b655…2a6f
6 touches
3 conflicts
0x1f396cee…862f
0x34b655…2a6f
6 touches
3 conflicts
0x1bba88cf…c18b
0x34b655…2a6f
6 touches
3 conflicts
0x1c59817b…07e8
0x34b655…2a6f
6 touches
3 conflicts
0x3acbb75e…f6f1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x3e0846cb8f…483067
Audit this contract →
← previous block·next block →recent activity