← previous blocknext block →recent activity
Analyzing
Block #76,522,722
8 transactions · 7 stateful · 2026-05-23 17:31:10 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,522,722 · 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
0xc6c7ecd4…0ec6
0x065c9d…c394
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0xbdf552f8…9f3c
0x065c9d…c394
3 touches
1 conflict
0x2e2ea792…7c83
0x065c9d…c394
3 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
2 touches
0 conflicts
0xbb1a8c56…d5b6
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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 0xc6c7ecd4d7…640ec6
Audit this contract →
← previous block·next block →recent activity