← previous blocknext block →recent activity
Analyzing
Block #73,271,095
20 transactions · 14 stateful · 2026-05-08 15:48:16 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,271,095 · 20 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
1w02w111w012w013w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x0cfb5d79…7ccb
0x2880ab…7b43
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
6 conflicts on slot 0xbd7e37a9b5…859eb5
Audit this contract →
← previous block·next block →recent activity