← previous blocknext block →recent activity
Analyzing
Block #73,751,420
8 transactions · 8 stateful · 2026-05-10 21:15:30 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,751,420 · 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x21d177a0…69c4
0x065c9d…c394
2 touches
0 conflicts
0x2a5e79a6…a9a7
0x065c9d…c394
2 touches
0 conflicts
0x6ce84762…6822
0x065c9d…c394
2 touches
0 conflicts
0x7fad5b05…ef35
0x065c9d…c394
2 touches
0 conflicts
0x8fb6026c…4dc8
0x065c9d…c394
2 touches
0 conflicts
0xb159af88…a9e7
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