← previous blocknext block →recent activity
Analyzing
Block #73,398,856
10 transactions · 9 stateful · 2026-05-09 05:58:20 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,398,856 · 10 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
1w04w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5aa24f04…5af6
0x065c9d…c394
4 touches
1 conflict
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x05c470b3…071c
0x065c9d…c394
3 touches
1 conflict
0xd4194a8f…b410
0x065c9d…c394
3 touches
1 conflict
0x2f353c16…0c80
0x065c9d…c394
2 touches
0 conflicts
0x2fddb12d…8273
0x065c9d…c394
2 touches
0 conflicts
0x6985f82a…75dc
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 0x5aa24f045d…9d5af6
Audit this contract →
← previous block·next block →recent activity