Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc69d5ef0f865497f0676146f74f388149bf8dab0abb0193df853c59a2fe382a

Tx prefix hash: f01a992931d33cb34351b47f7d61125907799db625ba6d2bff12beac55dabda4
Tx public key: a6efef93ed26ab37d9c31d31297286b6c47b9b90d0b4ce3178f5e9adacad27fc
Timestamp: 1700555735 Timestamp [UCT]: 2023-11-21 08:35:35 Age [y:d:h:m:s]: 01:061:04:23:48
Block: 896346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305083 RingCT/type: yes/0
Extra: 01a6efef93ed26ab37d9c31d31297286b6c47b9b90d0b4ce3178f5e9adacad27fc02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.657708720000 dcy

stealth address amount amount idx
00: cf1d61f5f4879bf6526ce01fec9e4ee0a1143f6a7d85bc8e8e142d49d764712f 0.657708720000 1352625 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": 896356, "vin": [ { "gen": { "height": 896346 } } ], "vout": [ { "amount": 657708720, "target": { "key": "cf1d61f5f4879bf6526ce01fec9e4ee0a1143f6a7d85bc8e8e142d49d764712f" } } ], "extra": [ 1, 166, 239, 239, 147, 237, 38, 171, 55, 217, 195, 29, 49, 41, 114, 134, 182, 196, 123, 155, 144, 208, 180, 206, 49, 120, 245, 233, 173, 172, 173, 39, 252, 2, 17, 0, 0, 0, 1, 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