← previous blocknext block →recent activity
Analyzing
Block #73,328,577
10 transactions · 9 stateful · 2026-05-08 22:10:48 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,328,577 · 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
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x2fc5406c…4e7b
0x065c9d…c394
2 touches
0 conflicts
0x610cc3a1…dae5
0x065c9d…c394
2 touches
0 conflicts
0x989043d8…77c3
0x065c9d…c394
2 touches
0 conflicts
0xa552fe6a…83e0
0x065c9d…c394
2 touches
0 conflicts
0xb9bb00a4…711f
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity