← previous blocknext block →recent activity
Analyzing
Block #105,673,225
16 transactions · 15 stateful · 2026-09-17 18:09:58 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,673,225 · 16 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
1w02w13w24w39w010w111w212w313w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05c1f7d7…280d
0x6f6493…b480
10 touches
10 conflicts
0x0d0b6186…c925
0x6f6493…b480
10 touches
10 conflicts
0x12fa952a…fd33
0x6f6493…b480
10 touches
10 conflicts
0x139938fa…5020
0x6f6493…b480
10 touches
10 conflicts
0x1d50ca82…9205
0x6f6493…b480
10 touches
10 conflicts
0x1e057316…b5d2
0x6f6493…b480
10 touches
10 conflicts
0x20152bae…8403
0x6f6493…b480
10 touches
10 conflicts
0x266b002b…f868
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 0x05c1f7d78a…c0280d
Audit this contract →
← previous block·next block →recent activity