Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0aaa926058753b43f63e8124f5f510236c2b6a361e3cb056bcefebe7590641d1

Tx prefix hash: dfa15b8fe766828d5e6cd882d76270efa023fc92433ae098699669e9fce932ae
Tx public key: b3e9b3fe5451266f9aec866fd03cb9de14513ddd6082c92a1854f0cd5c4e8f52
Timestamp: 1703786818 Timestamp [UCT]: 2023-12-28 18:06:58 Age [y:d:h:m:s]: 01:328:20:02:33
Block: 923140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493855 RingCT/type: yes/0
Extra: 01b3e9b3fe5451266f9aec866fd03cb9de14513ddd6082c92a1854f0cd5c4e8f5202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8aa6bd0505665516658f536bc097831a15842a8b59a87917fcb16c3a069f866a 0.600000000000 1380866 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": 923150, "vin": [ { "gen": { "height": 923140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aa6bd0505665516658f536bc097831a15842a8b59a87917fcb16c3a069f866a" } } ], "extra": [ 1, 179, 233, 179, 254, 84, 81, 38, 111, 154, 236, 134, 111, 208, 60, 185, 222, 20, 81, 61, 221, 96, 130, 201, 42, 24, 84, 240, 205, 92, 78, 143, 82, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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