Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8f1ca29158a4a4422824dc1d19b24276a0c675e83864feba8d029c70c8f67ba

Tx prefix hash: e91c065d208f600f64608c648a0d8e1bd1c15f131abdc18cb573392ebb8d93f7
Tx public key: 72e9441b7a105d4770d5dcca4d8316e1b1fff70c7db949d585e55b0be36d63af
Timestamp: 1733666137 Timestamp [UCT]: 2024-12-08 13:55:37 Age [y:d:h:m:s]: 00:116:21:17:09
Block: 1170758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83328 RingCT/type: yes/0
Extra: 0172e9441b7a105d4770d5dcca4d8316e1b1fff70c7db949d585e55b0be36d63af021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 472f2e0dca6408f60f29756b873f7930840fcff9bbd5018262102f1337eb69af 0.600000000000 1656491 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": 1170768, "vin": [ { "gen": { "height": 1170758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "472f2e0dca6408f60f29756b873f7930840fcff9bbd5018262102f1337eb69af" } } ], "extra": [ 1, 114, 233, 68, 27, 122, 16, 93, 71, 112, 213, 220, 202, 77, 131, 22, 225, 177, 255, 247, 12, 125, 185, 73, 213, 133, 229, 91, 11, 227, 109, 99, 175, 2, 17, 0, 0, 0, 7, 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