← previous blocknext block →recent activity
Analyzing
Block #76,444,433
8 transactions · 7 stateful · 2026-05-23 08:49:55 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,444,433 · 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e7a5b1d…d863
0x065c9d…c394
4 touches
1 conflict
0xa8b81bf5…a985
0x065c9d…c394
4 touches
1 conflict
0x276d63ad…10e9
0x065c9d…c394
3 touches
1 conflict
0x952ce6bb…c57a
0x065c9d…c394
3 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
2 touches
0 conflicts
0x9bf064a6…4f04
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
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 0x6e7a5b1da6…cfd863
Audit this contract →
← previous block·next block →recent activity