Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 061c700d1c1a80fbcb1eb13620ed62db1d42cb27cb7e4443f4c56f02fca2d402

Tx prefix hash: 116a765e9822c822eb8051cf3a8ca88b4bd0ab5e8e7de298d7fc44aca138b637
Tx public key: a1e04af779fda59071d72c94597275bf06af05d2c32cb0590cba21fbd191cdcd
Timestamp: 1581515317 Timestamp [UCT]: 2020-02-12 13:48:37 Age [y:d:h:m:s]: 05:266:18:44:00
Block: 63465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1341200 RingCT/type: yes/0
Extra: 01a1e04af779fda59071d72c94597275bf06af05d2c32cb0590cba21fbd191cdcd02110000000103d36d11000000000000000000

1 output(s) for total of 378.194250922000 dcy

stealth address amount amount idx
00: 2f856e7571b5167ebaa77749a0ff5c9f48c74473ffc6c29593dea9b36e6a9daf 378.194250922000 117021 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": 63475, "vin": [ { "gen": { "height": 63465 } } ], "vout": [ { "amount": 378194250922, "target": { "key": "2f856e7571b5167ebaa77749a0ff5c9f48c74473ffc6c29593dea9b36e6a9daf" } } ], "extra": [ 1, 161, 224, 74, 247, 121, 253, 165, 144, 113, 215, 44, 148, 89, 114, 117, 191, 6, 175, 5, 210, 195, 44, 176, 89, 12, 186, 33, 251, 209, 145, 205, 205, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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