← previous blocknext block →recent activity
Analyzing
Block #106,407,900
19 transactions · 19 stateful · 2026-09-20 07:49:56 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,407,900 · 19 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
1w02w13w24w39w010w111w212w313w414w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00d8cd6f…d81c
0x6f6493…b480
12 touches
15 conflicts
0x089fe53d…724f
0x6f6493…b480
12 touches
15 conflicts
0x12ec0dba…0e73
0x6f6493…b480
12 touches
15 conflicts
0x16a90511…970b
0x6f6493…b480
12 touches
15 conflicts
0x16f5115b…e5ce
0x6f6493…b480
12 touches
15 conflicts
0x19df045b…3bbd
0x6f6493…b480
12 touches
15 conflicts
0x1d00b725…0f82
0x6f6493…b480
12 touches
15 conflicts
0x2ba4ce5b…1904
0x6f6493…b480
12 touches
15 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
15 conflicts on slot 0x00d8cd6f61…d4d81c
Audit this contract →
← previous block·next block →recent activity