Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57af8322558191961343416c21b5f31a9ac8dd02a4d50cf80aed572fa4254816

Tx prefix hash: 7a512218c452295e8c37a5d31af65a9294814fb99204ee852ad1cfdcb8701487
Tx public key: cc17da8100a444bb610ae94c1e6dc4f02860df0e8996a1e9787275a573707da6
Timestamp: 1736278193 Timestamp [UCT]: 2025-01-07 19:29:53 Age [y:d:h:m:s]: 00:093:16:43:26
Block: 1192371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66763 RingCT/type: yes/0
Extra: 01cc17da8100a444bb610ae94c1e6dc4f02860df0e8996a1e9787275a573707da6021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae0f991fcc722bf62be63b6537a77aa5c69a867eae7fcf9246b7f7a1be4af729 0.600000000000 1678922 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": 1192381, "vin": [ { "gen": { "height": 1192371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae0f991fcc722bf62be63b6537a77aa5c69a867eae7fcf9246b7f7a1be4af729" } } ], "extra": [ 1, 204, 23, 218, 129, 0, 164, 68, 187, 97, 10, 233, 76, 30, 109, 196, 240, 40, 96, 223, 14, 137, 150, 161, 233, 120, 114, 117, 165, 115, 112, 125, 166, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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