Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcf63b32e4d02e994118ee9e34b2143c6eb8a715cd7bf9caf1cc0974f7329b57

Tx prefix hash: 9abaf5a275877cee1ce3f4d45a16dfda40b1f196109521743200dd4e1e97c1e3
Tx public key: 4bac552b47cb64a73961a62d1ae1cf099b1e13cd385550f4a0b6e74297ced33f
Timestamp: 1720300957 Timestamp [UCT]: 2024-07-06 21:22:37 Age [y:d:h:m:s]: 00:272:19:43:45
Block: 1060043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194934 RingCT/type: yes/0
Extra: 014bac552b47cb64a73961a62d1ae1cf099b1e13cd385550f4a0b6e74297ced33f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3acc9e6508ee74be5e52d8a5ba20241421ffdd0592f9ebd5e2ac33991e48ab69 0.600000000000 1530514 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": 1060053, "vin": [ { "gen": { "height": 1060043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3acc9e6508ee74be5e52d8a5ba20241421ffdd0592f9ebd5e2ac33991e48ab69" } } ], "extra": [ 1, 75, 172, 85, 43, 71, 203, 100, 167, 57, 97, 166, 45, 26, 225, 207, 9, 155, 30, 19, 205, 56, 85, 80, 244, 160, 182, 231, 66, 151, 206, 211, 63, 2, 17, 0, 0, 0, 2, 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