← previous blocknext block →recent activity
Analyzing
Block #73,810,999
16 transactions · 15 stateful · 2026-05-11 03:56:51 UTC
Parallelism
44/100
Blocked
67%
Avg conflicts / tx
2.31
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #73,810,999 · 16 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w28w39w410w511w612w113w214w715w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x4d87512b…897c
0x065c9d…c394
8 touches
6 conflicts
0x2f9624d5…ce01
0x065c9d…c394
6 touches
3 conflicts
0x95cff6d6…09af
0x065c9d…c394
6 touches
3 conflicts
0xfcaea661…bd93
0x065c9d…c394
4 touches
2 conflicts
0x3e184833…d237
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