Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 380cf477a71a63dc0e584f81c738117f9566c36a2e4e02e3f287fcd5d837ddd8

Tx prefix hash: 54649904085c185b356a14a59e45d4bacc546048831673ae055f51868c25cdcd
Tx public key: e7d42d3d59b873cba3b8ffbd48e91dbaf7a40e4683734b39fbed2adcf5d24ab9
Timestamp: 1713138423 Timestamp [UCT]: 2024-04-14 23:47:03 Age [y:d:h:m:s]: 00:362:20:54:02
Block: 1000643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259445 RingCT/type: yes/0
Extra: 01e7d42d3d59b873cba3b8ffbd48e91dbaf7a40e4683734b39fbed2adcf5d24ab90211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e62a4aaf670b2ff0777012f4f7eb6b65e7d106da7b5c82ff70c33b2fca03b5d 0.600000000000 1461141 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": 1000653, "vin": [ { "gen": { "height": 1000643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e62a4aaf670b2ff0777012f4f7eb6b65e7d106da7b5c82ff70c33b2fca03b5d" } } ], "extra": [ 1, 231, 212, 45, 61, 89, 184, 115, 203, 163, 184, 255, 189, 72, 233, 29, 186, 247, 164, 14, 70, 131, 115, 75, 57, 251, 237, 42, 220, 245, 210, 74, 185, 2, 17, 0, 0, 0, 3, 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