← previous blocknext block →recent activity
Analyzing
Block #92,275,439
25 transactions · 24 stateful · 2026-08-01 18:36:12 UTC
Parallelism
76/100
Blocked
46%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,275,439 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w28w19w310w011w112w213w314w415w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0eb63d5…743b
0x7b9256…1fb2
10 touches
10 conflicts
0xe1f61186…e2f8
0x754704…b603
10 touches
10 conflicts
0x00000000…0006
0x7b9256…1fb2
10 touches
10 conflicts
0x384fd8cc…0438
0x7b9256…1fb2
10 touches
10 conflicts
0x384fd8cc…0439
0x7b9256…1fb2
10 touches
10 conflicts
0x384fd8cc…043c
0x7b9256…1fb2
10 touches
10 conflicts
0xc0eb63d5…743a
0x7b9256…1fb2
10 touches
10 conflicts
0x177211e2…1c2d
0x754704…b603
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: 0x7b9256fd…e21fb2
10 conflicts on slot 0xc0eb63d598…71743b
Audit this contract →
← previous block·next block →recent activity