Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c1d209f549418eb40ba3086484826381bbb49bf95db84598399989a1320f029

Tx prefix hash: 049f779b55213475892e1a22fadf49a6e7ec4d54802add901814cd335a4d8ddd
Tx public key: a8d5bc1fd37c5b243154936ede470d4ca1f35b6147106aa780f9a5a94f450e1e
Timestamp: 1684861448 Timestamp [UCT]: 2023-05-23 17:04:08 Age [y:d:h:m:s]: 01:348:01:35:45
Block: 766495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509984 RingCT/type: yes/0
Extra: 01a8d5bc1fd37c5b243154936ede470d4ca1f35b6147106aa780f9a5a94f450e1e02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.771267103000 dcy

stealth address amount amount idx
00: a47a2b3004454ac15b381e165c849e019b8267835fe9251e3215f9074a9c776c 1.771267103000 1215540 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": 766505, "vin": [ { "gen": { "height": 766495 } } ], "vout": [ { "amount": 1771267103, "target": { "key": "a47a2b3004454ac15b381e165c849e019b8267835fe9251e3215f9074a9c776c" } } ], "extra": [ 1, 168, 213, 188, 31, 211, 124, 91, 36, 49, 84, 147, 110, 222, 71, 13, 76, 161, 243, 91, 97, 71, 16, 106, 167, 128, 249, 165, 169, 79, 69, 14, 30, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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