Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cde12ebe93fe8d8c1d3e470c479a7572e41f8147318a7ae6d119ee719e2a7f48

Tx prefix hash: 174aa6f60cb5f51aaecb5aac5afc3797719b98baa8d53f27776b779f43aa08e1
Tx public key: 6a2d09e2ed72201c5b013af7d773aad2abd1fade1b0e265b6b6a3f445193fae9
Timestamp: 1712089504 Timestamp [UCT]: 2024-04-02 20:25:04 Age [y:d:h:m:s]: 01:211:16:34:32
Block: 991944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409998 RingCT/type: yes/0
Extra: 016a2d09e2ed72201c5b013af7d773aad2abd1fade1b0e265b6b6a3f445193fae90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f46dc2184d09e1aa836792c3bb1150c4cc1ddc8662f10e4cca100012008f1de 0.600000000000 1452280 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": 991954, "vin": [ { "gen": { "height": 991944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f46dc2184d09e1aa836792c3bb1150c4cc1ddc8662f10e4cca100012008f1de" } } ], "extra": [ 1, 106, 45, 9, 226, 237, 114, 32, 28, 91, 1, 58, 247, 215, 115, 170, 210, 171, 209, 250, 222, 27, 14, 38, 91, 107, 106, 63, 68, 81, 147, 250, 233, 2, 17, 0, 0, 0, 1, 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