← previous blocknext block →recent activity
Analyzing
Block #73,523,009
8 transactions · 7 stateful · 2026-05-09 19:44:25 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,523,009 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb944d31e…61c2
0x065c9d…c394
3 touches
1 conflict
0x15af881a…41bc
0x065c9d…c394
3 touches
1 conflict
0x00d813a6…9f87
0x065c9d…c394
2 touches
0 conflicts
0x152c5818…53f5
0x065c9d…c394
2 touches
0 conflicts
0x161e3656…566b
0x065c9d…c394
2 touches
0 conflicts
0x22b3b2b0…3303
0x065c9d…c394
2 touches
0 conflicts
0x54c30e24…70dd
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity