Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a86d92e15939bc0b79b58fa3fc5300910c66e3b0ceb78a966528fb08ae46f81

Tx prefix hash: 3ed13a334dbb24a6846ccaa1af743a95042deb865da9b83976d5ca850e616a64
Tx public key: 3cdda820b67f8aa0e339cf6d045b6fe8d723501aeeb28548e58535dd396a3072
Timestamp: 1700178820 Timestamp [UCT]: 2023-11-16 23:53:40 Age [y:d:h:m:s]: 01:161:05:53:23
Block: 893240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376422 RingCT/type: yes/0
Extra: 013cdda820b67f8aa0e339cf6d045b6fe8d723501aeeb28548e58535dd396a307202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.673480571000 dcy

stealth address amount amount idx
00: 34b463bc81050481c909d54e7b25b8992e142257e2fe8647381c8acd14137fdd 0.673480571000 1349403 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": 893250, "vin": [ { "gen": { "height": 893240 } } ], "vout": [ { "amount": 673480571, "target": { "key": "34b463bc81050481c909d54e7b25b8992e142257e2fe8647381c8acd14137fdd" } } ], "extra": [ 1, 60, 221, 168, 32, 182, 127, 138, 160, 227, 57, 207, 109, 4, 91, 111, 232, 215, 35, 80, 26, 238, 178, 133, 72, 229, 133, 53, 221, 57, 106, 48, 114, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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