← previous blocknext block →recent activity
Analyzing
Block #106,018,611
22 transactions · 22 stateful · 2026-09-18 23:10:44 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
1.09
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,018,611 · 22 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
1w04w05w16w07w18w09w111w012w113w214w315w416w117w218w319w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x093898dc…ee4e
0x6f6493…b480
10 touches
10 conflicts
0x094d3b2f…ff0b
0x6f6493…b480
10 touches
10 conflicts
0x09d7c38c…579a
0x6f6493…b480
10 touches
10 conflicts
0x0d3c7cad…5286
0x6f6493…b480
10 touches
10 conflicts
0x1343ccf6…9c06
0x6f6493…b480
10 touches
10 conflicts
0x1cb7d0b0…2f81
0x6f6493…b480
10 touches
10 conflicts
0x24dfca1d…3997
0x6f6493…b480
10 touches
10 conflicts
0x259ae23d…0cb2
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 0x093898dce8…d1ee4e
Audit this contract →
← previous block·next block →recent activity