← previous blocknext block →recent activity
Analyzing
Block #73,213,620
14 transactions · 14 stateful · 2026-05-08 09:25:53 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,213,620 · 14 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
1w04w05w16w18w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0x1588e186…83b5
0xd32edf…ff58
3 touches
1 conflict
0x31415755…cc35
0x065c9d…c394
2 touches
0 conflicts
0xac73b081…0db2
0x065c9d…c394
2 touches
0 conflicts
0xb15a51f8…ed42
0x065c9d…c394
2 touches
0 conflicts
0xfd352f43…633e
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