← previous blocknext block →recent activity
Analyzing
Block #73,991,183
13 transactions · 10 stateful · 2026-05-11 23:58:02 UTC
Parallelism
46/100
Blocked
60%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,991,183 · 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
1w02w17w28w39w410w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x6f08361d…bda6
0x065c9d…c394
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x2480366d…aab6
0x065c9d…c394
2 touches
0 conflicts
0x4060981e…36d5
0x065c9d…c394
2 touches
0 conflicts
0xa9454d24…3a75
0x065c9d…c394
2 touches
0 conflicts
0xcc1243e4…572b
0x065c9d…c394
2 touches
0 conflicts
0xcfd12fb8…4a0a
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity