← previous blocknext block →recent activity
Analyzing
Block #106,469,209
14 transactions · 13 stateful · 2026-09-20 12:58:32 UTC
Parallelism
79/100
Blocked
54%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,469,209 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w26w19w010w111w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a2a3038…8939
0x6f6493…b480
6 touches
3 conflicts
0x0c7a0be0…05b6
0x6f6493…b480
6 touches
3 conflicts
0x1598e7f3…ad70
0x6f6493…b480
6 touches
3 conflicts
0x21f18e63…c393
0x6f6493…b480
6 touches
3 conflicts
0x23a7a226…e735
0x6f6493…b480
6 touches
3 conflicts
0x278191d2…5d7d
0x6f6493…b480
6 touches
3 conflicts
0x278191d2…5d81
0x6f6493…b480
6 touches
3 conflicts
0x2d2495b7…c0df
0x6f6493…b480
6 touches
3 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
3 conflicts on slot 0x0a2a303892…1e8939
Audit this contract →
← previous block·next block →recent activity