← previous blocknext block →recent activity
Analyzing
Block #105,851,904
21 transactions · 20 stateful · 2026-09-18 09:10:39 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,851,904 · 21 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
2w04w05w19w010w111w012w113w214w315w116w217w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01b72903…16f1
0x6f6493…b480
8 touches
6 conflicts
0x01b72903…16f5
0x6f6493…b480
8 touches
6 conflicts
0x06af5575…78e1
0x6f6493…b480
8 touches
6 conflicts
0x0d13d768…6a0b
0x6f6493…b480
8 touches
6 conflicts
0x0ec5ae7c…c35d
0x6f6493…b480
8 touches
6 conflicts
0x12fec20b…68c5
0x6f6493…b480
8 touches
6 conflicts
0x19fce226…5f24
0x6f6493…b480
8 touches
6 conflicts
0x1bd26b93…6599
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 0x01b72903fb…c616f1
Audit this contract →
← previous block·next block →recent activity