Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de0fe562924f6e4a8a3b68f7b73e3b333767c0fa123a2fe403fc3b22c79952d8

Tx prefix hash: 89bd72a587944d70910aca5c49ef6748add4c3d0572a37a542a875c9ec8e8f4c
Tx public key: aa3327aa94ca7eb09356104c8e5d6c22de311458d564881a8f39697a19315d83
Timestamp: 1708717332 Timestamp [UCT]: 2024-02-23 19:42:12 Age [y:d:h:m:s]: 01:034:02:46:52
Block: 964016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285398 RingCT/type: yes/0
Extra: 01aa3327aa94ca7eb09356104c8e5d6c22de311458d564881a8f39697a19315d8302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 253472167ec8db6a71efb2c5f79e5e20d2cdaa92c55a8596175038f23744aa39 0.600000000000 1423743 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": 964026, "vin": [ { "gen": { "height": 964016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "253472167ec8db6a71efb2c5f79e5e20d2cdaa92c55a8596175038f23744aa39" } } ], "extra": [ 1, 170, 51, 39, 170, 148, 202, 126, 176, 147, 86, 16, 76, 142, 93, 108, 34, 222, 49, 20, 88, 213, 100, 136, 26, 143, 57, 105, 122, 25, 49, 93, 131, 2, 17, 0, 0, 0, 1, 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