← previous blocknext block →recent activity
Analyzing
Block #73,161,232
10 transactions · 9 stateful · 2026-05-08 03:37:08 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,161,232 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x74920687…bfb0
0x065c9d…c394
3 touches
1 conflict
0x7b48d8b0…4381
0x065c9d…c394
3 touches
1 conflict
0xcc550b3a…db7b
0x065c9d…c394
3 touches
1 conflict
0x3237c2b9…efc4
0x065c9d…c394
3 touches
1 conflict
0x9aaed770…e2bd
0x065c9d…c394
3 touches
1 conflict
0xab8275c2…b87f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity