← previous blocknext block →recent activity
Analyzing
Block #76,490,696
8 transactions · 7 stateful · 2026-05-23 13:58:01 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,490,696 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x55949481…fb4b
0x065c9d…c394
3 touches
1 conflict
0x2a22b1ff…0b0c
0x065c9d…c394
2 touches
0 conflicts
0x31715516…332a
0x065c9d…c394
2 touches
0 conflicts
0x493e6c7e…67d6
0x065c9d…c394
2 touches
0 conflicts
0xb4717865…b6ce
0x065c9d…c394
2 touches
0 conflicts
0xbe8f43d8…949b
0x065c9d…c394
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
1 conflict on slot 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity