Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaccf559101e7b9d1f8b37c712adc313c4e2c040372381c3b3f70d1b353c4184

Tx prefix hash: 0c9cc14715edf27d5541017dfcd14465dbf3995cb41708702c7d85cba40d6248
Tx public key: dac73d80ba63c011b2296ec0fd00eaffbf2db71e535ab46d372bb8b902b3e88d
Timestamp: 1702182262 Timestamp [UCT]: 2023-12-10 04:24:22 Age [y:d:h:m:s]: 01:158:15:24:31
Block: 909846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374538 RingCT/type: yes/0
Extra: 01dac73d80ba63c011b2296ec0fd00eaffbf2db71e535ab46d372bb8b902b3e88d0211000000054b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45794e464def95f8fe3d3d182fddb3a35ecb4dce3011f1013a871a3364bbb3cd 0.600000000000 1366971 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": 909856, "vin": [ { "gen": { "height": 909846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45794e464def95f8fe3d3d182fddb3a35ecb4dce3011f1013a871a3364bbb3cd" } } ], "extra": [ 1, 218, 199, 61, 128, 186, 99, 192, 17, 178, 41, 110, 192, 253, 0, 234, 255, 191, 45, 183, 30, 83, 90, 180, 109, 55, 43, 184, 185, 2, 179, 232, 141, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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