Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad219bc61289438e3a42c8c206170e9cf1f8974cdaa5471681e57bb0685c935e

Tx prefix hash: 005acdd34d9b5b748343f0735945d254324d04c8e3e47bacfe509d98985a713f
Tx public key: cf35de0966c4fb04e38dee853a5667e084b4f42868b17d197f0edb99df24d863
Timestamp: 1708784032 Timestamp [UCT]: 2024-02-24 14:13:52 Age [y:d:h:m:s]: 01:059:15:17:34
Block: 964572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303652 RingCT/type: yes/0
Extra: 01cf35de0966c4fb04e38dee853a5667e084b4f42868b17d197f0edb99df24d86302110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37a7e7aa52897843b3909e0aaf18d2984fc6e92555594ad0df2d72c0416e7371 0.600000000000 1424313 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": 964582, "vin": [ { "gen": { "height": 964572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37a7e7aa52897843b3909e0aaf18d2984fc6e92555594ad0df2d72c0416e7371" } } ], "extra": [ 1, 207, 53, 222, 9, 102, 196, 251, 4, 227, 141, 238, 133, 58, 86, 103, 224, 132, 180, 244, 40, 104, 177, 125, 25, 127, 14, 219, 153, 223, 36, 216, 99, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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