Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af2143396c616753c91ef7ad46d7e87f0efd65a885753febb4087f84294f3656

Tx prefix hash: 8617bf16f83962b933bfa41be4b68e0555afdf263fd27d8a8f544a55a22836c1
Tx public key: cf880bf4cf15db5aa542128670b33a14b5c67d4c3bd0e1714134ac72e4e0a147
Timestamp: 1582090684 Timestamp [UCT]: 2020-02-19 05:38:04 Age [y:d:h:m:s]: 04:351:19:14:36
Block: 67830 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1143751 RingCT/type: yes/0
Extra: 01cf880bf4cf15db5aa542128670b33a14b5c67d4c3bd0e1714134ac72e4e0a14702110000001cd81c26c0000000000000000000

1 output(s) for total of 365.806871554000 dcy

stealth address amount amount idx
00: 1e4a880d156abc484ac700a51616d41e87f225fe6d38896503ad87d7d8b6e1f7 365.806871554000 124994 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": 67840, "vin": [ { "gen": { "height": 67830 } } ], "vout": [ { "amount": 365806871554, "target": { "key": "1e4a880d156abc484ac700a51616d41e87f225fe6d38896503ad87d7d8b6e1f7" } } ], "extra": [ 1, 207, 136, 11, 244, 207, 21, 219, 90, 165, 66, 18, 134, 112, 179, 58, 20, 181, 198, 125, 76, 59, 208, 225, 113, 65, 52, 172, 114, 228, 224, 161, 71, 2, 17, 0, 0, 0, 28, 216, 28, 38, 192, 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