← previous blocknext block →recent activity
Analyzing
Block #73,674,323
10 transactions · 9 stateful · 2026-05-10 12:35:15 UTC
Parallelism
40/100
Blocked
56%
Avg conflicts / tx
1.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,674,323 · 10 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w47w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ac31945…2c72
0x065c9d…c394
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8d42d58b…c64e
0x065c9d…c394
4 touches
1 conflict
0x4575587f…c286
0x065c9d…c394
3 touches
1 conflict
0x0cf06ef8…2ed3
0x065c9d…c394
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x1e9f5c98…3a40
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 0x0ac3194537…8f2c72
Audit this contract →
← previous block·next block →recent activity