← previous blocknext block →recent activity
Analyzing
Block #96,637,928
23 transactions · 18 stateful · 2026-08-17 00:53:37 UTC
Parallelism
87/100
Blocked
28%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,637,928 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w112w013w116w119w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe7b33fb…8efc
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0xdbcceb7f…1ea1
0x065c9d…c394
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0x45f562b2…9294
0x2b46c0…1669
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
3 conflicts on slot 0xbe7b33fbb5…a38efc
Audit this contract →
← previous block·next block →recent activity