← previous blocknext block →recent activity
Analyzing
Block #105,919,201
22 transactions · 21 stateful · 2026-09-18 14:50:13 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,919,201 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w111w012w113w214w317w018w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06a6617f…7629
0x6f6493…b480
8 touches
6 conflicts
0x14dbc8ec…ca2c
0x6f6493…b480
8 touches
6 conflicts
0x199ddb7e…8459
0x6f6493…b480
8 touches
6 conflicts
0x21ba40df…36c4
0x6f6493…b480
8 touches
6 conflicts
0x270beadb…c710
0x6f6493…b480
8 touches
6 conflicts
0x33a4ad88…2bb8
0x6f6493…b480
8 touches
6 conflicts
0x40e7c59f…55fe
0x6f6493…b480
8 touches
6 conflicts
0x49470e33…abd8
0x6f6493…b480
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: 0x6f6493e3…08b480
6 conflicts on slot 0x06a6617f58…9f7629
Audit this contract →
← previous block·next block →recent activity