Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 070ecf49c4784beb043df8dcae56308564e1e10697ba5de76a8c8a271fcff5ab

Tx prefix hash: fd7c25c08095becabd41a0c9cb27b6afabab428ba3c532df6735c33a183aaaa3
Tx public key: cdaa3162c7cd340909ad5aaf7daad95723fcdf3483cae88bde806fe74dca5fce
Timestamp: 1696452400 Timestamp [UCT]: 2023-10-04 20:46:40 Age [y:d:h:m:s]: 02:035:12:48:08
Block: 862528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 545032 RingCT/type: yes/0
Extra: 01cdaa3162c7cd340909ad5aaf7daad95723fcdf3483cae88bde806fe74dca5fce021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.851308014000 dcy

stealth address amount amount idx
00: 1aa43fb2f53448f1a2f29e4c585c66c7b6fdf2a2cb13b5de130cdc3ba25053d2 0.851308014000 1316952 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": 862538, "vin": [ { "gen": { "height": 862528 } } ], "vout": [ { "amount": 851308014, "target": { "key": "1aa43fb2f53448f1a2f29e4c585c66c7b6fdf2a2cb13b5de130cdc3ba25053d2" } } ], "extra": [ 1, 205, 170, 49, 98, 199, 205, 52, 9, 9, 173, 90, 175, 125, 170, 217, 87, 35, 252, 223, 52, 131, 202, 232, 139, 222, 128, 111, 231, 77, 202, 95, 206, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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