← previous blocknext block →recent activity
Analyzing
Block #73,383,303
14 transactions · 10 stateful · 2026-05-09 04:14:43 UTC
Parallelism
79/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,383,303 · 14 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
2w08w19w2
- 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
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x7f81fb82…633e
0x065c9d…c394
2 touches
0 conflicts
0xb4b5d64d…2ce4
0x065c9d…c394
2 touches
0 conflicts
0xe0a9b70c…c027
0x065c9d…c394
2 touches
0 conflicts
0xa7fe0d97…ae1c
0x2a68ba…90c5
2 touches
0 conflicts
0xe038916c…b1be
0x2a68ba…90c5
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