Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfd6ad64fffc23aac89f2f59aeb14aeb1cc2437fbdef31f2b61f8844176a97dc

Tx prefix hash: 2d43b427a98184ca4355ee862c01a878d1693ca6d0165b4f63ccec6eb053d595
Tx public key: 1f52792cc02e0a6ce09230f1200974d96c39d8989dc40df9a55839bcb1aa4b52
Timestamp: 1703794983 Timestamp [UCT]: 2023-12-28 20:23:03 Age [y:d:h:m:s]: 01:326:23:25:19
Block: 923205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492536 RingCT/type: yes/0
Extra: 011f52792cc02e0a6ce09230f1200974d96c39d8989dc40df9a55839bcb1aa4b520211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b01b43ff72a3a92a3384d07ea6d5cd6055af29294b9fd65d3583c1cac7b5941 0.600000000000 1380931 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": 923215, "vin": [ { "gen": { "height": 923205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b01b43ff72a3a92a3384d07ea6d5cd6055af29294b9fd65d3583c1cac7b5941" } } ], "extra": [ 1, 31, 82, 121, 44, 192, 46, 10, 108, 224, 146, 48, 241, 32, 9, 116, 217, 108, 57, 216, 152, 157, 196, 13, 249, 165, 88, 57, 188, 177, 170, 75, 82, 2, 17, 0, 0, 0, 7, 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