← previous blocknext block →recent activity
Analyzing
Block #73,213,939
19 transactions · 13 stateful · 2026-05-08 09:28:00 UTC
Parallelism
89/100
Blocked
15%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,213,939 · 19 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
7w09w011w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6fb58f4…f809
0x065c9d…c394
4 touches
1 conflict
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x03c07de3…580e
0x065c9d…c394
3 touches
1 conflict
0x4cc5afb7…6f60
0x065c9d…c394
3 touches
1 conflict
0xec8516ee…591c
0x065c9d…c394
3 touches
1 conflict
0x3c83127d…1c86
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
1 conflict on slot 0xb6fb58f4ac…50f809
Audit this contract →
← previous block·next block →recent activity