Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ed87c2c97e3bcc4a372b3a609564f7efe78d8da7ba61e6a3ab76ebddf569dbd

Tx prefix hash: 0d8a7d89b58c933da8e4231bb77f1dde6b2049772bb2e386752f7b7f928c79d0
Tx public key: 61a5d0e86bf0fee1cfc64f90b5f218a6ad580137c50ddfc41e287758c98dcc6a
Timestamp: 1647441335 Timestamp [UCT]: 2022-03-16 14:35:35 Age [y:d:h:m:s]: 02:247:19:57:12
Block: 459736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 696601 RingCT/type: yes/0
Extra: 0161a5d0e86bf0fee1cfc64f90b5f218a6ad580137c50ddfc41e287758c98dcc6a021100000014d3fcec30000000000000000000

1 output(s) for total of 18.397010389000 dcy

stealth address amount amount idx
00: 3ec57a2cd96c47e2c7c4df3311d83b648b0b1b39826abf432815fc713b1e52fc 18.397010389000 876551 of 0

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": 459746, "vin": [ { "gen": { "height": 459736 } } ], "vout": [ { "amount": 18397010389, "target": { "key": "3ec57a2cd96c47e2c7c4df3311d83b648b0b1b39826abf432815fc713b1e52fc" } } ], "extra": [ 1, 97, 165, 208, 232, 107, 240, 254, 225, 207, 198, 79, 144, 181, 242, 24, 166, 173, 88, 1, 55, 197, 13, 223, 196, 30, 40, 119, 88, 201, 141, 204, 106, 2, 17, 0, 0, 0, 20, 211, 252, 236, 48, 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