Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 834dfd9dd177980a484861eace424d0ae58e329b451a848f24ef587fb7ab51b2

Tx prefix hash: e2070b95717faf4aef5378f140b4560e2cbcc592b1aab00f9c1072d2e7a65c67
Tx public key: 41fbd295b0e878ee74aa5331f6544b6cc2fcbb937ab11409b2a30ffced8aacbf
Timestamp: 1703002284 Timestamp [UCT]: 2023-12-19 16:11:24 Age [y:d:h:m:s]: 01:334:00:14:30
Block: 916646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497559 RingCT/type: yes/0
Extra: 0141fbd295b0e878ee74aa5331f6544b6cc2fcbb937ab11409b2a30ffced8aacbf02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ff6361b1e0c2eccb795311f3691e6cc585a041bb886734d9db309822fa8bf78 0.600000000000 1374204 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": 916656, "vin": [ { "gen": { "height": 916646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ff6361b1e0c2eccb795311f3691e6cc585a041bb886734d9db309822fa8bf78" } } ], "extra": [ 1, 65, 251, 210, 149, 176, 232, 120, 238, 116, 170, 83, 49, 246, 84, 75, 108, 194, 252, 187, 147, 122, 177, 20, 9, 178, 163, 15, 252, 237, 138, 172, 191, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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