← previous blocknext block →recent activity
Analyzing
Block #73,375,534
23 transactions · 18 stateful · 2026-05-09 03:23:04 UTC
Parallelism
78/100
Blocked
44%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,375,534 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w19w010w116w217w318w420w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xaf6f2510…fa51
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x6af306bb…2e81
0x3bd359…433a
4 touches
1 conflict
0x1c354dc0…96de
0x754704…b603
4 touches
1 conflict
0xf91b744e…9117
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity