Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aa2f23b13ccfd74bfc4ada69d9a2f05bec05450def5b84e42c878a1000b5457

Tx prefix hash: 02015abb5f1d5b764804852a46b69042479bd247edc550cff8833bcf6f7be515
Tx public key: c2c202cedf8b0dbff49b8489c9cca6fcec7f6319ab5cb532f157c7501f2c0639
Timestamp: 1727705305 Timestamp [UCT]: 2024-09-30 14:08:25 Age [y:d:h:m:s]: 00:114:09:59:06
Block: 1121446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81751 RingCT/type: yes/0
Extra: 01c2c202cedf8b0dbff49b8489c9cca6fcec7f6319ab5cb532f157c7501f2c0639021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 945cdb8cc86a763f9cd9fd4cba5f9080dbe5d8f41e7ce027ada766f1b75a05e9 0.600000000000 1603713 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": 1121456, "vin": [ { "gen": { "height": 1121446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "945cdb8cc86a763f9cd9fd4cba5f9080dbe5d8f41e7ce027ada766f1b75a05e9" } } ], "extra": [ 1, 194, 194, 2, 206, 223, 139, 13, 191, 244, 155, 132, 137, 201, 204, 166, 252, 236, 127, 99, 25, 171, 92, 181, 50, 241, 87, 199, 80, 31, 44, 6, 57, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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