Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a378ae15e18e4242f8d77ce403e4dc94a5e637b03c662e5a43368e38cd7cf80

Tx prefix hash: 838cf2b9b57e5e962722509d33f5e86a4006e6f9e523ebe1b6daf72962f6e737
Tx public key: e7374b7352f0caf2f684d84c65166f1006a8c8818274782450d451e5f76b9859
Timestamp: 1707408268 Timestamp [UCT]: 2024-02-08 16:04:28 Age [y:d:h:m:s]: 00:318:04:28:33
Block: 953156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227836 RingCT/type: yes/0
Extra: 01e7374b7352f0caf2f684d84c65166f1006a8c8818274782450d451e5f76b985902110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 043fec77d335accac27fa69fc35ef2aed6e2f8926dd9d749bd598a5e3bd1843e 0.600000000000 1412328 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": 953166, "vin": [ { "gen": { "height": 953156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "043fec77d335accac27fa69fc35ef2aed6e2f8926dd9d749bd598a5e3bd1843e" } } ], "extra": [ 1, 231, 55, 75, 115, 82, 240, 202, 242, 246, 132, 216, 76, 101, 22, 111, 16, 6, 168, 200, 129, 130, 116, 120, 36, 80, 212, 81, 229, 247, 107, 152, 89, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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