← previous blocknext block →recent activity
Analyzing
Block #105,619,606
38 transactions · 34 stateful · 2026-09-17 13:40:01 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,619,606 · 38 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
1w02w13w25w26w07w18w29w310w415w016w117w018w119w220w321w422w525w336w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa518e77d…675c
0x6f6493…b480
12 touches
15 conflicts
0x0fe959d8…07cc
0x6f6493…b480
12 touches
15 conflicts
0x2e811370…dd77
0x6f6493…b480
12 touches
15 conflicts
0x4b987dfe…545c
0x6f6493…b480
12 touches
15 conflicts
0x620f009f…99f7
0x6f6493…b480
12 touches
15 conflicts
0x78bc7df0…3018
0x6f6493…b480
12 touches
15 conflicts
0x9bc3dbf2…636e
0x6f6493…b480
12 touches
15 conflicts
0xa518e77d…6758
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 0xa518e77dc3…c1675c
Audit this contract →
← previous block·next block →recent activity