← previous blocknext block →recent activity
Analyzing
Block #73,985,517
5 transactions · 4 stateful · 2026-05-11 23:19:51 UTC
Parallelism
60/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,985,517 · 5 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
0x08c22af2…16dc
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3d7acd23…e056
0x065c9d…c394
3 touches
1 conflict
0x42ebe4bf…92c0
0x065c9d…c394
2 touches
0 conflicts
0x4adb57e3…9c94
0x065c9d…c394
2 touches
0 conflicts
0x68f70a39…b4dd
0x065c9d…c394
2 touches
0 conflicts
0x6ccbee17…1eed
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
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 0x08c22af2ec…8616dc
Audit this contract →
← previous block·next block →recent activity