← previous blocknext block →recent activity
Analyzing
Block #73,867,626
15 transactions · 12 stateful · 2026-05-11 10:14:04 UTC
Parallelism
47/100
Blocked
67%
Avg conflicts / tx
1.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,867,626 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w18w39w410w511w612w7
- 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
12 touches
15 conflicts
0xb159af88…a9e7
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa3a2f50d…ffdd
0x065c9d…c394
4 touches
1 conflict
0xd18e39e4…a854
0x065c9d…c394
4 touches
1 conflict
0xe04a6afc…7fb5
0x065c9d…c394
4 touches
1 conflict
0xb1d6f076…a3c5
0x065c9d…c394
3 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