Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79c10b945bbc379601989d8af283d0ce9f7bfd1548c416d75bb6e1e114bf7d85

Tx prefix hash: 1df64627366dc9c70db2818e9fa4c3e33b5b9ebb15731e9f5b6318507f9b7665
Tx public key: d74d630579d4b2d1d6b2fdcdd3861294df0fbf34c265a66fe65a9229eb7588e3
Timestamp: 1703340831 Timestamp [UCT]: 2023-12-23 14:13:51 Age [y:d:h:m:s]: 01:320:12:57:10
Block: 919439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487934 RingCT/type: yes/0
Extra: 01d74d630579d4b2d1d6b2fdcdd3861294df0fbf34c265a66fe65a9229eb7588e30211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e7e47f58f14d9e129520145203276ea8466bdc57bec6733b8704d98ac2d700b 0.600000000000 1377111 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": 919449, "vin": [ { "gen": { "height": 919439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e7e47f58f14d9e129520145203276ea8466bdc57bec6733b8704d98ac2d700b" } } ], "extra": [ 1, 215, 77, 99, 5, 121, 212, 178, 209, 214, 178, 253, 205, 211, 134, 18, 148, 223, 15, 191, 52, 194, 101, 166, 111, 230, 90, 146, 41, 235, 117, 136, 227, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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