← previous blocknext block →recent activity
Analyzing
Block #105,575,068
20 transactions · 19 stateful · 2026-09-17 09:55:50 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,575,068 · 20 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
1w02w13w24w36w07w111w012w113w214w315w418w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28d319b2…fa67
0x6f6493…b480
10 touches
10 conflicts
0x3833c24b…d643
0x6f6493…b480
10 touches
10 conflicts
0x71edc019…22ca
0x6f6493…b480
10 touches
10 conflicts
0x8e93ba5f…d180
0x6f6493…b480
10 touches
10 conflicts
0xaf1247d1…7c73
0x6f6493…b480
10 touches
10 conflicts
0xe3c68c64…aa04
0x6f6493…b480
10 touches
10 conflicts
0xe3c68c64…aa08
0x6f6493…b480
10 touches
10 conflicts
0xf6068816…c359
0x6f6493…b480
10 touches
10 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
10 conflicts on slot 0x28d319b2d9…f3fa67
Audit this contract →
← previous block·next block →recent activity