Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccbe04ddaefc5cfe35d55f765fd378a2cab882e9989339c5059f9e5e78200d75

Tx prefix hash: 6d140dd9e13e6067c72cde1ca10c12c2fc3dd10d58c394d5f9145e1212417de4
Tx public key: 9a635129cf3e7ea0e490d912e00226fde8969bf6a219afb7c56b3e409109e336
Timestamp: 1707318762 Timestamp [UCT]: 2024-02-07 15:12:42 Age [y:d:h:m:s]: 01:270:23:54:07
Block: 952421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452441 RingCT/type: yes/0
Extra: 019a635129cf3e7ea0e490d912e00226fde8969bf6a219afb7c56b3e409109e33602110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3fe91d94fc34906b8d2886e28ab2c31f4b6dcf99bd1089be3ac6618bdf892a3 0.600000000000 1411401 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": 952431, "vin": [ { "gen": { "height": 952421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3fe91d94fc34906b8d2886e28ab2c31f4b6dcf99bd1089be3ac6618bdf892a3" } } ], "extra": [ 1, 154, 99, 81, 41, 207, 62, 126, 160, 228, 144, 217, 18, 224, 2, 38, 253, 232, 150, 155, 246, 162, 25, 175, 183, 197, 107, 62, 64, 145, 9, 227, 54, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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