← previous blocknext block →recent activity
Analyzing
Block #73,987,631
8 transactions · 8 stateful · 2026-05-11 23:34:01 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,987,631 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x6aa624fd…a84d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xa9587f54…1f78
0xd32edf…ff58
3 touches
1 conflict
0x303f9621…72b3
0x065c9d…c394
2 touches
1 conflict
0xd0db5b2c…ca76
0x065c9d…c394
2 touches
0 conflicts
0xd528ac96…584d
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 0x6f08361da9…89bda6
Audit this contract →
← previous block·next block →recent activity