← previous blocknext block →recent activity
Analyzing
Block #106,100,906
17 transactions · 16 stateful · 2026-09-19 06:04:52 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,100,906 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w111w212w314w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x087ef620…186e
0x6f6493…b480
8 touches
6 conflicts
0x0d3cd62c…d4ef
0x6f6493…b480
8 touches
6 conflicts
0x439d0427…d130
0x6f6493…b480
8 touches
6 conflicts
0x46c68714…4cb3
0x6f6493…b480
8 touches
6 conflicts
0x4cbfcf56…9a01
0x6f6493…b480
8 touches
6 conflicts
0x517a6c74…c8ec
0x6f6493…b480
8 touches
6 conflicts
0x5a77fe0f…342d
0x6f6493…b480
8 touches
6 conflicts
0x67fa0bd1…fab2
0x6f6493…b480
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: 0x6f6493e3…08b480
6 conflicts on slot 0x087ef62022…44186e
Audit this contract →
← previous block·next block →recent activity