Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5a0ab89ef1edd35bd44aa7db597a8a33b8293ded8559b140fa698cd1a6d317a

Tx prefix hash: 11a06a556ead95bb5e5303efae0b48c376ea2a8af94e4864e53d6c0977ef1ebe
Tx public key: 2aa8e356fc0d6a400c13cd662d842178a0ffcbeae7d3bddbf87ba93023dcfb3f
Timestamp: 1747913424 Timestamp [UCT]: 2025-05-22 11:30:24 Age [y:d:h:m:s]: 00:251:03:34:51
Block: 1288436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177112 RingCT/type: yes/0
Extra: 012aa8e356fc0d6a400c13cd662d842178a0ffcbeae7d3bddbf87ba93023dcfb3f0211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d34b35cfb87e54795ebce4c6966bdbfa3f44b91803c3b14cff68f16f9f28c74 0.600000000000 1775903 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 dinasty-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": 1288446, "vin": [ { "gen": { "height": 1288436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d34b35cfb87e54795ebce4c6966bdbfa3f44b91803c3b14cff68f16f9f28c74" } } ], "extra": [ 1, 42, 168, 227, 86, 252, 13, 106, 64, 12, 19, 205, 102, 45, 132, 33, 120, 160, 255, 203, 234, 231, 211, 189, 219, 248, 123, 169, 48, 35, 220, 251, 63, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8