Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf83e538b61d46f7b844fd4f99ad5d5ec8a1fc2f6ec522338b599b32feac61f6

Tx prefix hash: cb736c8099eeaed8550e809e96f5ed0f81fe09e13a4284647384b15389c00246
Tx public key: 90a022e6432270a2dc0b348911ab553ac3a46c7eef48cbc4c2c9d1aced7bc97c
Timestamp: 1661147121 Timestamp [UCT]: 2022-08-22 05:45:21 Age [y:d:h:m:s]: 03:070:19:45:54
Block: 571171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 830441 RingCT/type: yes/0
Extra: 0190a022e6432270a2dc0b348911ab553ac3a46c7eef48cbc4c2c9d1aced7bc97c021100000001faf35c9c000000000000000000

1 output(s) for total of 7.860921763000 dcy

stealth address amount amount idx
00: 3f715704acb6d196f5ae34ae74a7b6fb59e830d6e3f0430348b15bf95410b6e4 7.860921763000 1004373 of 0

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": 571181, "vin": [ { "gen": { "height": 571171 } } ], "vout": [ { "amount": 7860921763, "target": { "key": "3f715704acb6d196f5ae34ae74a7b6fb59e830d6e3f0430348b15bf95410b6e4" } } ], "extra": [ 1, 144, 160, 34, 230, 67, 34, 112, 162, 220, 11, 52, 137, 17, 171, 85, 58, 195, 164, 108, 126, 239, 72, 203, 196, 194, 201, 209, 172, 237, 123, 201, 124, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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