← previous blocknext block →recent activity
Analyzing
Block #76,212,560
14 transactions · 13 stateful · 2026-05-22 07:05:46 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,212,560 · 14 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
1w04w15w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0012cded…25d0
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x0d8fac93…c478
0x065c9d…c394
3 touches
1 conflict
0x22ee94ac…aee8
0x065c9d…c394
3 touches
1 conflict
0x63002cd2…a354
0x065c9d…c394
2 touches
0 conflicts
0x9206c78d…8519
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 0x0012cded91…f625d0
Audit this contract →
← previous block·next block →recent activity