← previous blocknext block →recent activity
Analyzing
Block #105,582,172
17 transactions · 17 stateful · 2026-09-17 10:31:35 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,582,172 · 17 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
1w02w15w06w17w28w39w410w011w012w113w114w215w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01952762…65fd
0x6f6493…b480
10 touches
10 conflicts
0x02c24a7d…6f09
0x6f6493…b480
10 touches
10 conflicts
0x0a7c9461…9019
0x6f6493…b480
10 touches
10 conflicts
0x137a6bf5…7636
0x6f6493…b480
10 touches
10 conflicts
0x21d86470…0d92
0x6f6493…b480
10 touches
10 conflicts
0x22f545a2…0fb0
0x6f6493…b480
10 touches
10 conflicts
0x23880f9b…5361
0x6f6493…b480
10 touches
10 conflicts
0x2fdc00d4…7934
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 0x01952762ed…f965fd
Audit this contract →
← previous block·next block →recent activity