← previous blocknext block →recent activity
Analyzing
Block #92,220,368
21 transactions · 20 stateful · 2026-08-01 13:59:12 UTC
Parallelism
81/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,220,368 · 21 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
1w02w14w26w311w012w113w214w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfce06e9e…8589
0x7b9256…1fb2
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0x0258008c…45c4
0x7b9256…1fb2
8 touches
6 conflicts
0x0258008c…45c5
0x7b9256…1fb2
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0xfce06e9e…8585
0x7b9256…1fb2
8 touches
6 conflicts
0xfce06e9e…8586
0x7b9256…1fb2
8 touches
6 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: 0x7b9256fd…e21fb2
6 conflicts on slot 0xfce06e9e4c…238589
Audit this contract →
← previous block·next block →recent activity