← previous blocknext block →recent activity
Analyzing
Block #92,821,052
16 transactions · 16 stateful · 2026-08-03 16:21:36 UTC
Parallelism
75/100
Blocked
19%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,821,052 · 16 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
7w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa30a349e…bec8
0x065c9d…c394
3 touches
1 conflict
0xc2ec2ddf…e406
0x065c9d…c394
3 touches
1 conflict
0x5c694165…1107
0x065c9d…c394
3 touches
1 conflict
0xcb643582…2626
0x3bd359…433a
2 touches
0 conflicts
0xa0d3faac…ae01
0x754704…b603
2 touches
0 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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity