← previous blocknext block →recent activity
Analyzing
Block #73,399,339
20 transactions · 17 stateful · 2026-05-09 06:01:33 UTC
Parallelism
50/100
Blocked
53%
Avg conflicts / tx
1.7
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,399,339 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w110w211w312w013w414w515w616w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0x03833adf…b96f
0x065c9d…c394
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x63e48b…53f2
2 touches
0 conflicts
0x00000000…0003
0x63e48b…53f2
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity