Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 664dff7cf506bc5b9ac610a3c7273dae72b23fd06b4f5e4fba2fd1cf6d0f5d47

Tx prefix hash: e457e96dadac491ac85ff6ffa6f274773eafa044a9e3f2be64ecba4d102cae74
Tx public key: 0dff10bbc7e4404c26353a261ab6181642a0c9efb18c353d7666802728aecdb6
Timestamp: 1707881907 Timestamp [UCT]: 2024-02-14 03:38:27 Age [y:d:h:m:s]: 01:041:08:32:36
Block: 957076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290589 RingCT/type: yes/0
Extra: 010dff10bbc7e4404c26353a261ab6181642a0c9efb18c353d7666802728aecdb60211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1df3bdb20c3d497a8db66e65f1190259f6ebe061b51d3769277622cf93d6d83c 0.600000000000 1416390 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": 957086, "vin": [ { "gen": { "height": 957076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1df3bdb20c3d497a8db66e65f1190259f6ebe061b51d3769277622cf93d6d83c" } } ], "extra": [ 1, 13, 255, 16, 187, 199, 228, 64, 76, 38, 53, 58, 38, 26, 182, 24, 22, 66, 160, 201, 239, 177, 140, 53, 61, 118, 102, 128, 39, 40, 174, 205, 182, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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