← previous blocknext block →recent activity
Analyzing
Block #76,196,307
9 transactions · 7 stateful · 2026-05-22 05:17:44 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,196,307 · 9 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
1w02w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e567126…d068
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb670b59d…5e82
0x065c9d…c394
3 touches
1 conflict
0x7576d4a0…3e2f
0x065c9d…c394
3 touches
1 conflict
0xb3963556…0f63
0x065c9d…c394
2 touches
0 conflicts
0xe4eb4313…8fe8
0x065c9d…c394
2 touches
0 conflicts
0xec8724c4…62f7
0x065c9d…c394
2 touches
0 conflicts
0xf3d7a307…4d63
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 0x8e56712680…31d068
Audit this contract →
← previous block·next block →recent activity