← previous blocknext block →recent activity
Analyzing
Block #73,398,553
17 transactions · 17 stateful · 2026-05-09 05:56:19 UTC
Parallelism
53/100
Blocked
41%
Avg conflicts / tx
1.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,398,553 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w210w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x03833adf…b96f
0x065c9d…c394
4 touches
1 conflict
0x809ef576…a5a7
0x065c9d…c394
3 touches
1 conflict
0xe7acee56…58e5
0x065c9d…c394
3 touches
1 conflict
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
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity