← previous blocknext block →recent activity
Analyzing
Block #73,446,992
7 transactions · 7 stateful · 2026-05-09 11:18:38 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,446,992 · 7 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
1w02w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x148cb976…2354
0x065c9d…c394
3 touches
1 conflict
0x9b1bf429…e002
0x065c9d…c394
2 touches
0 conflicts
0xa974698c…b601
0x065c9d…c394
2 touches
0 conflicts
0xaae36ada…f073
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 0x4d87512b00…43897c
Audit this contract →
← previous block·next block →recent activity