← previous blocknext block →recent activity
Analyzing
Block #73,383,243
8 transactions · 6 stateful · 2026-05-09 04:14:19 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,383,243 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb159af88…a9e7
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3b6f6113…7581
0x065c9d…c394
2 touches
0 conflicts
0x77401294…c9f0
0x065c9d…c394
2 touches
0 conflicts
0x889b6f56…5c1b
0x065c9d…c394
2 touches
0 conflicts
0x8a23261d…4afd
0x065c9d…c394
2 touches
0 conflicts
0xaab85040…0bcc
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity