← previous blocknext block →recent activity
Analyzing
Block #73,210,038
24 transactions · 16 stateful · 2026-05-08 09:02:09 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,210,038 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w116w217w318w419w5
- 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
0x1705a6be…18ee
0xd32edf…ff58
3 touches
1 conflict
0x49fc7fd6…249c
0x065c9d…c394
2 touches
0 conflicts
0x7e3bdb67…221d
0x065c9d…c394
2 touches
0 conflicts
0xb6796ecc…c864
0x065c9d…c394
2 touches
0 conflicts
0xe2bf7c6d…563b
0x065c9d…c394
2 touches
0 conflicts
0xe36631bb…7b20
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