Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d6857f5deb57fc7a455fca9dda1f4d29f50aa504c7db45e95b7d50b6fe2b6265

Tx prefix hash: 54ed9553be1d7dba9f96035a4b1d95427d2e2b3e11d38c1a8352d4689e003fe6
Tx public key: cc4c053c69d6b883717cc442cc1c507ad9c33e9963f5a22caa910f024afc6975
Timestamp: 1774412000 Timestamp [UTC]: 2026-03-25 04:13:20 Age [y:d:h:m:s]: 00:234:04:39:02
Block: 1505254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172772 RingCT/type: yes/0
Extra: 01cc4c053c69d6b883717cc442cc1c507ad9c33e9963f5a22caa910f024afc6975021100000006f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c5a8d6a4c119a006c834b0fdf3d67db43b09b5fc7f464f29aafa8c15a1b9cea5 0.000600000000 1994986 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1505264, "vin": [ { "gen": { "height": 1505254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5a8d6a4c119a006c834b0fdf3d67db43b09b5fc7f464f29aafa8c15a1b9cea5" } } ], "extra": [ 1, 204, 76, 5, 60, 105, 214, 184, 131, 113, 124, 196, 66, 204, 28, 80, 122, 217, 195, 62, 153, 99, 245, 162, 44, 170, 145, 15, 2, 74, 252, 105, 117, 2, 17, 0, 0, 0, 6, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: