← previous blocknext block →recent activity
Analyzing
Block #73,336,024
14 transactions · 14 stateful · 2026-05-08 23:00:16 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,336,024 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w27w38w29w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f08361d…bda6
0x065c9d…c394
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x7ed46b4f…8980
0xd32edf…ff58
3 touches
1 conflict
0x64c9db47…2b3e
0x065c9d…c394
2 touches
0 conflicts
0x979e5818…c903
0x065c9d…c394
2 touches
0 conflicts
0xc787c16e…6f19
0x065c9d…c394
2 touches
0 conflicts
0xda655e6f…fbb1
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
15 conflicts on slot 0x6f08361da9…89bda6
Audit this contract →
← previous block·next block →recent activity