Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1534c641c5d4ac8668c86ce06d63e590064fc69ac5d91fa416653a1861c3e44

Tx prefix hash: b39b12bb9ca987497c8da3bde95b37d05d19a16556fe764c67d8ab0f962e9b4e
Tx public key: a0a79a02a671f257fb59d10fd1166cf3e27e78187ba79651ede86d30f4a72eb3
Timestamp: 1741604868 Timestamp [UCT]: 2025-03-10 11:07:48 Age [y:d:h:m:s]: 00:254:20:53:41
Block: 1236218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179887 RingCT/type: yes/0
Extra: 01a0a79a02a671f257fb59d10fd1166cf3e27e78187ba79651ede86d30f4a72eb3021100000011007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c04ea80778d2c799bde0ad6dd83ca252a9b410f1b30eae34313937583b9b1969 0.600000000000 1723163 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": 1236228, "vin": [ { "gen": { "height": 1236218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c04ea80778d2c799bde0ad6dd83ca252a9b410f1b30eae34313937583b9b1969" } } ], "extra": [ 1, 160, 167, 154, 2, 166, 113, 242, 87, 251, 89, 209, 15, 209, 22, 108, 243, 226, 126, 120, 24, 123, 167, 150, 81, 237, 232, 109, 48, 244, 167, 46, 179, 2, 17, 0, 0, 0, 17, 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