← previous blocknext block →recent activity
Analyzing
Block #106,004,105
30 transactions · 26 stateful · 2026-09-18 21:57:44 UTC
Parallelism
87/100
Blocked
35%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,004,105 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w112w215w016w120w221w023w124w325w329w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xdd021d12…362a
0x065c9d…c394
5 touches
3 conflicts
0xdd8c5978…ac09
0x065c9d…c394
5 touches
3 conflicts
0x1e4bf9ea…75dd
0x34b655…2a6f
4 touches
1 conflict
0x1e9a3afd…a6e5
0x34b655…2a6f
4 touches
1 conflict
0x345b6a56…6e3f
0x34b655…2a6f
4 touches
1 conflict
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity