Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a535428516c26fbfd5c2c57e44790c2fe21e1cdad3290a9b9a53849a2d0fcfd

Tx prefix hash: 69cc9f54694d16a5dc552a1839140cec33ba986750ea1db851cf64f2a4f936d3
Tx public key: 83f4156a6f4255cf0790e58843dc64bece85ccf2d6ae9cd879402dd5b5998bd3
Timestamp: 1732792083 Timestamp [UCT]: 2024-11-28 11:08:03 Age [y:d:h:m:s]: 00:130:02:37:03
Block: 1163505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92788 RingCT/type: yes/0
Extra: 0183f4156a6f4255cf0790e58843dc64bece85ccf2d6ae9cd879402dd5b5998bd30211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa38a2ccb9118ac53f61e2a109aec3b7ec64d1b434e7783e419fd42c902bab82 0.600000000000 1649172 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": 1163515, "vin": [ { "gen": { "height": 1163505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa38a2ccb9118ac53f61e2a109aec3b7ec64d1b434e7783e419fd42c902bab82" } } ], "extra": [ 1, 131, 244, 21, 106, 111, 66, 85, 207, 7, 144, 229, 136, 67, 220, 100, 190, 206, 133, 204, 242, 214, 174, 156, 216, 121, 64, 45, 213, 181, 153, 139, 211, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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