Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38024304e3b2261ff63689deca9c54197deb0ad512efa2dfea99d81f49f13108

Tx prefix hash: d85e1660ff31ea0ba8f98d37d71efb5421163341eea915116ac2cf84a6b22a61
Tx public key: ade68c6e3f7b94b341a9b4f8d9f5b7a0de77fc86931cd25a90e79b95baf75233
Timestamp: 1645547013 Timestamp [UCT]: 2022-02-22 16:23:33 Age [y:d:h:m:s]: 02:304:09:57:15
Block: 444160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737007 RingCT/type: yes/0
Extra: 01ade68c6e3f7b94b341a9b4f8d9f5b7a0de77fc86931cd25a90e79b95baf75233021100000006c9067537000000000000000000

1 output(s) for total of 20.716378047000 dcy

stealth address amount amount idx
00: 3da72323216ad1fa435e3e97ddf9edd42f78fa02fce778c09419d919f4059520 20.716378047000 857369 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": 444170, "vin": [ { "gen": { "height": 444160 } } ], "vout": [ { "amount": 20716378047, "target": { "key": "3da72323216ad1fa435e3e97ddf9edd42f78fa02fce778c09419d919f4059520" } } ], "extra": [ 1, 173, 230, 140, 110, 63, 123, 148, 179, 65, 169, 180, 248, 217, 245, 183, 160, 222, 119, 252, 134, 147, 28, 210, 90, 144, 231, 155, 149, 186, 247, 82, 51, 2, 17, 0, 0, 0, 6, 201, 6, 117, 55, 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