← previous blocknext block →recent activity
Analyzing
Block #76,090,282
16 transactions · 11 stateful · 2026-05-21 17:31:38 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,090,282 · 16 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
1w02w13w05w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1f81369…3ed1
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x47bc83d3…1489
0x065c9d…c394
2 touches
0 conflicts
0x69dd7480…130c
0x065c9d…c394
2 touches
0 conflicts
0xa87480dd…905b
0x065c9d…c394
2 touches
0 conflicts
0xcc844732…a5f1
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 0xb1f8136920…ab3ed1
Audit this contract →
← previous block·next block →recent activity