Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29e81ef0e70701518ba0fb3854e08c96c49b3f41c62c5ce3769de7dc56fae597

Tx prefix hash: f63881f2e022f16175501a48793f29cbfc54a7bc1d907849725d8a4bf6e915f1
Tx public key: 6e6b7b2253efe80df79da7b5de92cd826883e33ae17363bf2807405412bbbf2f
Timestamp: 1719945388 Timestamp [UCT]: 2024-07-02 18:36:28 Age [y:d:h:m:s]: 00:317:09:58:12
Block: 1057102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226823 RingCT/type: yes/0
Extra: 016e6b7b2253efe80df79da7b5de92cd826883e33ae17363bf2807405412bbbf2f02110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72adc3bb18ec6493d3a1dede76ee2f18a85e99e50d6f8393e6c8eb451a6d348c 0.600000000000 1527531 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": 1057112, "vin": [ { "gen": { "height": 1057102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72adc3bb18ec6493d3a1dede76ee2f18a85e99e50d6f8393e6c8eb451a6d348c" } } ], "extra": [ 1, 110, 107, 123, 34, 83, 239, 232, 13, 247, 157, 167, 181, 222, 146, 205, 130, 104, 131, 227, 58, 225, 115, 99, 191, 40, 7, 64, 84, 18, 187, 191, 47, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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