← previous blocknext block →recent activity
Analyzing
Block #73,263,642
11 transactions · 9 stateful · 2026-05-08 14:58:35 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,263,642 · 11 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
1w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x44351239…ac63
0x065c9d…c394
2 touches
0 conflicts
0x61608543…27a5
0x065c9d…c394
2 touches
0 conflicts
0x69e60a1a…f4ad
0x065c9d…c394
2 touches
0 conflicts
0x81e39bf1…ee84
0x065c9d…c394
2 touches
0 conflicts
0x9c86a366…e809
0x065c9d…c394
2 touches
0 conflicts
0xb55d56f9…082f
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity