← previous blocknext block →recent activity
Analyzing
Block #106,342,011
18 transactions · 16 stateful · 2026-09-20 02:18:20 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,342,011 · 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
1w02w13w27w09w010w111w212w313w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c275713…8932
0x6f6493…b480
9 touches
10 conflicts
0x1c275713…8936
0x6f6493…b480
9 touches
10 conflicts
0x1dfe99ce…b095
0x6f6493…b480
9 touches
10 conflicts
0x209cf733…2ff1
0x6f6493…b480
9 touches
10 conflicts
0x28f7820f…e9d1
0x6f6493…b480
9 touches
10 conflicts
0x2aa28f66…5d79
0x6f6493…b480
9 touches
10 conflicts
0x38659e99…4e0b
0x6f6493…b480
9 touches
10 conflicts
0x3b18766a…6b3e
0x6f6493…b480
9 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 0x1c27571398…f28932
Audit this contract →
← previous block·next block →recent activity