← previous blocknext block →recent activity
Analyzing
Block #73,990,797
10 transactions · 8 stateful · 2026-05-11 23:55:24 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,990,797 · 10 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
4w05w06w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf537eaa0…73c8
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x34814806…e709
0xd42a27…01c7
2 touches
0 conflicts
0x85531ec5…7434
0xd42a27…01c7
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x85531ec5…7438
0xd42a27…01c7
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 0xf537eaa0c6…3873c8
Audit this contract →
← previous block·next block →recent activity