Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 919a94efe64065cb703d3eb2de84bae375c4ec70806ef7e740e0fcc8575cbf43

Tx prefix hash: 81890c326843a11840031e99b913f34ed4eedb103d906ef9321c396b39180208
Tx public key: 7ee5c14c28f447c79af382dd26f9e9f4d78531df419c24b8c5162e1ed421d69f
Timestamp: 1717949925 Timestamp [UCT]: 2024-06-09 16:18:45 Age [y:d:h:m:s]: 00:232:03:17:44
Block: 1040568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165868 RingCT/type: yes/0
Extra: 017ee5c14c28f447c79af382dd26f9e9f4d78531df419c24b8c5162e1ed421d69f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c7ca1374c120747728f912782fc5ca5b69e56e04754fd41bb36dcd9b3117a91 0.600000000000 1509225 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": 1040578, "vin": [ { "gen": { "height": 1040568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c7ca1374c120747728f912782fc5ca5b69e56e04754fd41bb36dcd9b3117a91" } } ], "extra": [ 1, 126, 229, 193, 76, 40, 244, 71, 199, 154, 243, 130, 221, 38, 249, 233, 244, 215, 133, 49, 223, 65, 156, 36, 184, 197, 22, 46, 30, 212, 33, 214, 159, 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