← previous blocknext block →recent activity
Analyzing
Block #105,581,525
20 transactions · 18 stateful · 2026-09-17 10:28:19 UTC
Parallelism
75/100
Blocked
56%
Avg conflicts / tx
1.25
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,581,525 · 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
1w02w13w24w35w49w010w111w212w313w414w017w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x586bf431…8579
0x6f6493…b480
10 touches
10 conflicts
0x8476ee6f…1131
0x6f6493…b480
10 touches
10 conflicts
0xc73542df…c3f9
0x6f6493…b480
10 touches
10 conflicts
0xfd665090…300d
0x6f6493…b480
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xec85b41e…7c92
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
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 0x586bf4317a…4e8579
Audit this contract →
← previous block·next block →recent activity