← previous blocknext block →recent activity
Analyzing
Block #106,272,710
18 transactions · 17 stateful · 2026-09-19 20:29:36 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,272,710 · 18 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
1w02w19w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01ea369f…80e0
0x6f6493…b480
10 touches
10 conflicts
0x01ea369f…80e4
0x6f6493…b480
10 touches
10 conflicts
0x0264c950…cc8c
0x6f6493…b480
10 touches
10 conflicts
0x07f7a032…5331
0x6f6493…b480
10 touches
10 conflicts
0x0bc184f6…3ce4
0x6f6493…b480
10 touches
10 conflicts
0x17bd8ec4…02e6
0x6f6493…b480
10 touches
10 conflicts
0x1a9b074c…ffee
0x6f6493…b480
10 touches
10 conflicts
0x205a22c8…45a5
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 0x01ea369fd0…c280e0
Audit this contract →
← previous block·next block →recent activity