Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a087b94d2e18ccaed234e35834e51997ce5a7f790301f587fd8358daa3e5479f

Tx prefix hash: 6ae507e1e348feeff1ad915410ad5bc53a94e3793554e849c9d99db393240dc7
Tx public key: 411efe8ff46dfb111b78601329f057358791d3cc9d8f1e2f6361a12b7db11d27
Timestamp: 1704997733 Timestamp [UCT]: 2024-01-11 18:28:53 Age [y:d:h:m:s]: 01:124:04:11:42
Block: 933164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349885 RingCT/type: yes/0
Extra: 01411efe8ff46dfb111b78601329f057358791d3cc9d8f1e2f6361a12b7db11d270211000000117a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81a5b92747d644fdf4c4028c58a3f50d6f7110d15fea6810c3c81242561698a6 0.600000000000 1391122 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": 933174, "vin": [ { "gen": { "height": 933164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81a5b92747d644fdf4c4028c58a3f50d6f7110d15fea6810c3c81242561698a6" } } ], "extra": [ 1, 65, 30, 254, 143, 244, 109, 251, 17, 27, 120, 96, 19, 41, 240, 87, 53, 135, 145, 211, 204, 157, 143, 30, 47, 99, 97, 161, 43, 125, 177, 29, 39, 2, 17, 0, 0, 0, 17, 122, 156, 244, 199, 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