← previous blocknext block →recent activity
Analyzing
Block #106,008,484
20 transactions · 15 stateful · 2026-09-18 22:19:46 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,008,484 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w08w412w513w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xaf59c69d…c904
0x37db7f…ec7b
8 touches
6 conflicts
0x3d6c26e5…1b45
0x34b655…2a6f
8 touches
6 conflicts
0xd58e5c6b…7188
0x34b655…2a6f
8 touches
6 conflicts
0xe5250927…ef6a
0x34b655…2a6f
8 touches
6 conflicts
0x3f25409b…f92b
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x9ee73aa5…0d70
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity