Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ec462dc78937a0c7b2be033cec0374def7c34944543a03888f93e7f2ec35c4f

Tx prefix hash: 1e4b6bceeb5b959d93b4c05329ea934eb2b2c0c5b51f51ecb391ca3d08e7b21b
Tx public key: ce196f541647f5298ea41c944201436d43d90b2be3760713f1197329012421af
Timestamp: 1712100111 Timestamp [UCT]: 2024-04-02 23:21:51 Age [y:d:h:m:s]: 01:014:04:41:18
Block: 992028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271139 RingCT/type: yes/0
Extra: 01ce196f541647f5298ea41c944201436d43d90b2be3760713f1197329012421af0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc0cc313d7625cf2c2ccdf4a5ade6f4fc80efc3a4b7565d82b17e12f38cc83fe 0.600000000000 1452364 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": 992038, "vin": [ { "gen": { "height": 992028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc0cc313d7625cf2c2ccdf4a5ade6f4fc80efc3a4b7565d82b17e12f38cc83fe" } } ], "extra": [ 1, 206, 25, 111, 84, 22, 71, 245, 41, 142, 164, 28, 148, 66, 1, 67, 109, 67, 217, 11, 43, 227, 118, 7, 19, 241, 25, 115, 41, 1, 36, 33, 175, 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