← previous blocknext block →recent activity
Analyzing
Block #73,697,831
10 transactions · 8 stateful · 2026-05-10 15:13:48 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,697,831 · 10 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa49e8688…bbac
0x065c9d…c394
2 touches
0 conflicts
0xcd3c8154…0e90
0x065c9d…c394
2 touches
0 conflicts
0xa9988419…9f45
0x34b655…2a6f
2 touches
0 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity