← previous blocknext block →recent activity
Analyzing
Block #76,448,547
10 transactions · 9 stateful · 2026-05-23 09:17:19 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,448,547 · 10 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
1w02w13w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb30adcea…1e11
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x396849a1…9ee6
0x065c9d…c394
4 touches
1 conflict
0x5a400cd3…3ea2
0x065c9d…c394
3 touches
1 conflict
0x4a480a99…5567
0x065c9d…c394
3 touches
1 conflict
0xa17ec269…7cdd
0x1d1325…2305
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 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity