Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ad61b999287f47a5a58902a56fa38f81037c90d9de14e856900c95119e6ae38

Tx prefix hash: db17420d62506929b9862c5297b863b8e1bd0cc596997b6c66b468e334e217e9
Tx public key: 03bc9ea1759d56e6e95108b1e654693d07aa4a426fcc2a6ece75ca1662b90774
Timestamp: 1720649884 Timestamp [UCT]: 2024-07-10 22:18:04 Age [y:d:h:m:s]: 00:249:04:30:37
Block: 1062946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178028 RingCT/type: yes/0
Extra: 0103bc9ea1759d56e6e95108b1e654693d07aa4a426fcc2a6ece75ca1662b90774021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 831d5d9e6907f42891208f67301aec389fd2f70e930e239803e1fce4fbae5013 0.600000000000 1533457 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": 1062956, "vin": [ { "gen": { "height": 1062946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "831d5d9e6907f42891208f67301aec389fd2f70e930e239803e1fce4fbae5013" } } ], "extra": [ 1, 3, 188, 158, 161, 117, 157, 86, 230, 233, 81, 8, 177, 230, 84, 105, 61, 7, 170, 74, 66, 111, 204, 42, 110, 206, 117, 202, 22, 98, 185, 7, 116, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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