← previous blocknext block →recent activity
Analyzing
Block #106,109,637
24 transactions · 23 stateful · 2026-09-19 06:48:49 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,109,637 · 24 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
1w02w13w24w09w010w113w214w315w016w117w218w319w420w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08f05e63…b51e
0x6f6493…b480
10 touches
10 conflicts
0x16329945…b4ad
0x6f6493…b480
10 touches
10 conflicts
0x1bfe0188…c9dd
0x6f6493…b480
10 touches
10 conflicts
0x1c554157…ce22
0x6f6493…b480
10 touches
10 conflicts
0x267bf451…04e7
0x6f6493…b480
10 touches
10 conflicts
0x28e09f11…43c0
0x6f6493…b480
10 touches
10 conflicts
0x29a297a7…614c
0x6f6493…b480
10 touches
10 conflicts
0x35973e09…3958
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 0x08f05e6354…f7b51e
Audit this contract →
← previous block·next block →recent activity