← previous blocknext block →recent activity
Analyzing
Block #76,483,638
7 transactions · 6 stateful · 2026-05-23 13:10:56 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,483,638 · 7 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa3225c51…2c9e
0x065c9d…c394
3 touches
1 conflict
0xae845300…054f
0x065c9d…c394
3 touches
1 conflict
0xb4e7314a…9cba
0x065c9d…c394
3 touches
1 conflict
0x2b20a052…6e61
0x065c9d…c394
3 touches
1 conflict
0x397493fc…6b38
0x065c9d…c394
3 touches
1 conflict
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 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity