← previous blocknext block →recent activity
Analyzing
Block #73,273,396
19 transactions · 16 stateful · 2026-05-08 16:03:34 UTC
Parallelism
74/100
Blocked
31%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,273,396 · 19 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
1w08w09w110w111w212w313w4
- 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
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x069e5ebf…0707
0x065c9d…c394
2 touches
0 conflicts
0x0981e562…1c27
0x065c9d…c394
2 touches
0 conflicts
0x3009fc65…54bd
0x065c9d…c394
2 touches
0 conflicts
0x3facc409…6233
0x065c9d…c394
2 touches
0 conflicts
0x9b36e005…7edf
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity