← previous blocknext block →recent activity
Analyzing
Block #106,014,954
19 transactions · 17 stateful · 2026-09-18 22:52:19 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,014,954 · 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
1w02w13w28w39w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b21ef5…e9c9
0x6f6493…b480
11 touches
15 conflicts
0x19ae096f…b10e
0x6f6493…b480
11 touches
15 conflicts
0x263bc68d…e2d1
0x6f6493…b480
11 touches
15 conflicts
0x352fa71e…307b
0x6f6493…b480
11 touches
15 conflicts
0x36dada12…428e
0x6f6493…b480
11 touches
15 conflicts
0x44c9788c…f440
0x6f6493…b480
11 touches
15 conflicts
0x578c2dde…980f
0x6f6493…b480
11 touches
15 conflicts
0x5a2a9dbc…56f2
0x6f6493…b480
11 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 0x07b21ef5e5…68e9c9
Audit this contract →
← previous block·next block →recent activity