Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac34083340908d541bf896283da5d175c8a5dc506e434c7a1cf3fd00fd8260fc

Tx prefix hash: f665d6c6d7beac7d9111fe911021021107ad357a9b69f2a7d36a5dcf6db5c573
Tx public key: 08b4dd663f5b564908b6da7d930b29e39552dc20e720b3cc04eff401bbe888fb
Timestamp: 1720700711 Timestamp [UCT]: 2024-07-11 12:25:11 Age [y:d:h:m:s]: 00:308:20:07:55
Block: 1063370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220676 RingCT/type: yes/0
Extra: 0108b4dd663f5b564908b6da7d930b29e39552dc20e720b3cc04eff401bbe888fb021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8daa19dbedde8ea9b3c675e5a4ad194d9881cc02ddf94fc4490e5cbe93f9a576 0.600000000000 1533885 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": 1063380, "vin": [ { "gen": { "height": 1063370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8daa19dbedde8ea9b3c675e5a4ad194d9881cc02ddf94fc4490e5cbe93f9a576" } } ], "extra": [ 1, 8, 180, 221, 102, 63, 91, 86, 73, 8, 182, 218, 125, 147, 11, 41, 227, 149, 82, 220, 32, 231, 32, 179, 204, 4, 239, 244, 1, 187, 232, 136, 251, 2, 17, 0, 0, 0, 8, 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