← previous blocknext block →recent activity
Analyzing
Block #73,336,160
10 transactions · 9 stateful · 2026-05-08 23:01:09 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,336,160 · 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
1w05w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xc9bab560…63d1
0x065c9d…c394
4 touches
1 conflict
0xed382b82…e0e8
0x065c9d…c394
3 touches
1 conflict
0xe5760559…c800
0x065c9d…c394
3 touches
1 conflict
0x5a4db224…eda5
0x065c9d…c394
2 touches
0 conflicts
0x7b3a3f30…f0fc
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
1 conflict on slot 0xf537eaa0c6…3873c8
Audit this contract →
← previous block·next block →recent activity