← previous blocknext block →recent activity
Analyzing
Block #73,307,921
13 transactions · 11 stateful · 2026-05-08 19:53:17 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,307,921 · 13 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
1w03w04w18w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x48659b74…dbd1
0x065c9d…c394
2 touches
0 conflicts
0x4d89687b…49f2
0x065c9d…c394
2 touches
0 conflicts
0x58a26e8e…cc26
0x065c9d…c394
2 touches
0 conflicts
0x81d2e592…76e1
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 0x0b390c6160…02dc07
Audit this contract →
← previous block·next block →recent activity