← previous blocknext block →recent activity
Analyzing
Block #105,858,604
20 transactions · 20 stateful · 2026-09-18 09:44:22 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,858,604 · 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
1w02w13w25w06w17w08w19w210w315w416w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x851145…3f07
10 touches
10 conflicts
0xdf93c009…d51f
0x851145…3f07
10 touches
10 conflicts
0x8a3fecf6…b414
0xc8689a…ee79
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x259ee49c…49df
0x34ae4d…3fc5
8 touches
6 conflicts
0x61218f00…5108
0x34ae4d…3fc5
8 touches
6 conflicts
0xd8fd2add…50fc
0x34ae4d…3fc5
8 touches
6 conflicts
0xc73fd549…2e28
0x851145…3f07
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: 0x851145ea…9f3f07
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity