Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad5bd2243b0ee899ed8f720bb543ef515e7ff4fa450f430b38d573f2cf5de785

Tx prefix hash: fc26ac2fb94e06e7fb9a0137bc7102f4db51b8b9d066fc9e18a876c15919f7c8
Tx public key: 41f97bcee84fa93e19e1d0286ff883325ce90a26caf7c2116c625e324153508c
Timestamp: 1738466552 Timestamp [UCT]: 2025-02-02 03:22:32 Age [y:d:h:m:s]: 00:292:21:05:35
Block: 1210223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207084 RingCT/type: yes/0
Extra: 0141f97bcee84fa93e19e1d0286ff883325ce90a26caf7c2116c625e324153508c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa9d8edebb09886aabc3a34d01731b67b0b10b43667515b6b406fda839f525df 0.600000000000 1696974 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": 1210233, "vin": [ { "gen": { "height": 1210223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa9d8edebb09886aabc3a34d01731b67b0b10b43667515b6b406fda839f525df" } } ], "extra": [ 1, 65, 249, 123, 206, 232, 79, 169, 62, 25, 225, 208, 40, 111, 248, 131, 50, 92, 233, 10, 38, 202, 247, 194, 17, 108, 98, 94, 50, 65, 83, 80, 140, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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