← previous blocknext block →recent activity
Analyzing
Block #73,214,031
7 transactions · 6 stateful · 2026-05-08 09:28:37 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,214,031 · 7 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
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xab760535…5df2
0x065c9d…c394
4 touches
1 conflict
0xd7fc1d07…a279
0x065c9d…c394
3 touches
1 conflict
0x31ad4e9f…772c
0x065c9d…c394
3 touches
1 conflict
0xf6798805…8faa
0x065c9d…c394
3 touches
1 conflict
0x52b4484c…ef4d
0x065c9d…c394
3 touches
1 conflict
0xdc880f33…1732
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 0xbd7e37a9b5…859eb5
Audit this contract →
← previous block·next block →recent activity