← previous blocknext block →recent activity
Analyzing
Block #105,672,145
18 transactions · 18 stateful · 2026-09-17 18:04:31 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,672,145 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w19w010w111w212w313w414w515w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0035e482…323e
0x6f6493…b480
12 touches
15 conflicts
0x02dc45e6…93c1
0x6f6493…b480
12 touches
15 conflicts
0x176990a3…d674
0x6f6493…b480
12 touches
15 conflicts
0x1e38c01b…5ecb
0x6f6493…b480
12 touches
15 conflicts
0x3936f121…826c
0x6f6493…b480
12 touches
15 conflicts
0x4a5bf12d…09a5
0x6f6493…b480
12 touches
15 conflicts
0x6183df10…c68f
0x6f6493…b480
12 touches
15 conflicts
0x65ecaf5e…1cd4
0x6f6493…b480
12 touches
15 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
15 conflicts on slot 0x0035e4820c…63323e
Audit this contract →
← previous block·next block →recent activity