← previous blocknext block →recent activity
Analyzing
Block #73,047,335
25 transactions · 18 stateful · 2026-05-07 14:59:35 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,047,335 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w19w213w314w415w316w417w518w623w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
10 touches
10 conflicts
0x7f189cf6…afab
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x01d8737a…61b2
0x065c9d…c394
5 touches
3 conflicts
0xce59842c…ab75
0x065c9d…c394
5 touches
3 conflicts
0x4e5ebbf7…ae70
0xc8689a…ee79
4 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity