← previous blocknext block →recent activity
Analyzing
Block #73,337,646
13 transactions · 12 stateful · 2026-05-08 23:11:02 UTC
Parallelism
46/100
Blocked
67%
Avg conflicts / tx
1.92
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,337,646 · 13 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
1w02w13w14w15w26w37w48w59w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
6 touches
3 conflicts
0x006a75a7…2153
0x065c9d…c394
6 touches
3 conflicts
0x48f53825…282e
0x065c9d…c394
5 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x29e81973…9a04
0x065c9d…c394
4 touches
1 conflict
0x8e6f638b…fee9
0x065c9d…c394
4 touches
1 conflict
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity