Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e4b5240261affbdd0e4daf69c87d334d94dc880968727e447b39aac96c0154f

Tx prefix hash: 225d57263f5df7a361dbfd4962c4e132330401291bb1dbf2ee2de33a7dc10d50
Tx public key: 71d2963ce2b4655a4bc730ef01e52ec5fe54c995b040d243f9701f7743b8724b
Timestamp: 1709060637 Timestamp [UCT]: 2024-02-27 19:03:57 Age [y:d:h:m:s]: 01:034:11:01:08
Block: 966870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285621 RingCT/type: yes/0
Extra: 0171d2963ce2b4655a4bc730ef01e52ec5fe54c995b040d243f9701f7743b8724b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce65dc2ab9ecda631c13ae6cb1dcca370443f8d0ac9d037cf132fbf2b36dd67b 0.600000000000 1426641 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": 966880, "vin": [ { "gen": { "height": 966870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce65dc2ab9ecda631c13ae6cb1dcca370443f8d0ac9d037cf132fbf2b36dd67b" } } ], "extra": [ 1, 113, 210, 150, 60, 226, 180, 101, 90, 75, 199, 48, 239, 1, 229, 46, 197, 254, 84, 201, 149, 176, 64, 210, 67, 249, 112, 31, 119, 67, 184, 114, 75, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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