← previous blocknext block →recent activity
Analyzing
Block #73,038,611
10 transactions · 7 stateful · 2026-05-07 14:01:30 UTC
Parallelism
60/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,038,611 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x566fb836…ba37
0x065c9d…c394
4 touches
1 conflict
0x0da08c60…c6f8
0x065c9d…c394
2 touches
0 conflicts
0x31415755…cc35
0x065c9d…c394
2 touches
0 conflicts
0x4fd9c3a2…e7f5
0x065c9d…c394
2 touches
0 conflicts
0x67306e3b…87f8
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity