← previous blocknext block →recent activity
Analyzing
Block #73,297,213
7 transactions · 7 stateful · 2026-05-08 18:42:01 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,297,213 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf2b8564…f576
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0xa64a938b…8073
0x065c9d…c394
3 touches
1 conflict
0x0aba6b6a…7246
0x065c9d…c394
3 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
2 touches
0 conflicts
0xad323e0f…50db
0x065c9d…c394
2 touches
0 conflicts
0xbcb0ec39…5de1
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 0xaf2b8564b5…44f576
Audit this contract →
← previous block·next block →recent activity