← previous blocknext block →recent activity
Analyzing
Block #106,307,817
18 transactions · 17 stateful · 2026-09-19 23:26:15 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,307,817 · 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
1w02w13w27w08w19w210w311w415w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeca4c0c3…b7fb
0x6f6493…b480
10 touches
10 conflicts
0xc6bbcb93…319e
0x6f6493…b480
10 touches
10 conflicts
0xc9301272…ad3e
0x6f6493…b480
10 touches
10 conflicts
0xccccb426…c62f
0x6f6493…b480
10 touches
10 conflicts
0xce9e9117…f82b
0x6f6493…b480
10 touches
10 conflicts
0xce9e9117…f82f
0x6f6493…b480
10 touches
10 conflicts
0xe46ff990…252c
0x6f6493…b480
10 touches
10 conflicts
0x1f975177…07ed
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 0xeca4c0c356…7cb7fb
Audit this contract →
← previous block·next block →recent activity