← previous blocknext block →recent activity
Analyzing
Block #106,924,243
54 transactions · 35 stateful · 2026-09-22 03:09:46 UTC
Parallelism
89/100
Blocked
49%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,924,243 · 54 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w110w113w014w115w216w017w226w231w337w243w345w246w348w449w552w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25445267…a756
0x34b655…2a6f
10 touches
10 conflicts
0xea2d1275…76c8
0x34b655…2a6f
8 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x327466db…3e17
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
6 touches
3 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
10 conflicts on slot 0x254452676f…dea756
Audit this contract →
← previous block·next block →recent activity