Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8053341681e560da7ccf358643c6e70d4c6a267535770aa02daf73e944894ab0

Tx prefix hash: f6bfc0c76facc8c7dc8ddc9e65606764484d7a095b02e4d812657c2e860ac584
Tx public key: 67bd1048578a35c70db9a55b6ae3545bd5cbc78622bae88cb2420bdd22e53c4a
Timestamp: 1716065952 Timestamp [UCT]: 2024-05-18 20:59:12 Age [y:d:h:m:s]: 00:360:15:59:39
Block: 1024938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257827 RingCT/type: yes/0
Extra: 0167bd1048578a35c70db9a55b6ae3545bd5cbc78622bae88cb2420bdd22e53c4a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96261a35642fc5cb177cd018811d98cb2d8894bd2b8e996772c7593127f8e9d4 0.600000000000 1491073 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": 1024948, "vin": [ { "gen": { "height": 1024938 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96261a35642fc5cb177cd018811d98cb2d8894bd2b8e996772c7593127f8e9d4" } } ], "extra": [ 1, 103, 189, 16, 72, 87, 138, 53, 199, 13, 185, 165, 91, 106, 227, 84, 91, 213, 203, 199, 134, 34, 186, 232, 140, 178, 66, 11, 221, 34, 229, 60, 74, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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