Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9aa05dc61ff6891cab7c8df791fa162004513bdaf28eab523969b9e2ac08b0b

Tx prefix hash: ccc348dd0657ad318f8ff98bc2a0c4bed50e26c7cf38c57f0aa0e4b19a7ee529
Tx public key: 07aff90ec7c2b0cbc982a2197804fb84e0900fdbbe321e6c91b2d08c9cf7bf7b
Timestamp: 1583346450 Timestamp [UCT]: 2020-03-04 18:27:30 Age [y:d:h:m:s]: 04:295:04:45:35
Block: 76393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105379 RingCT/type: yes/0
Extra: 0107aff90ec7c2b0cbc982a2197804fb84e0900fdbbe321e6c91b2d08c9cf7bf7b02110000003d026b59f3000000000000000000

1 output(s) for total of 342.672358737000 dcy

stealth address amount amount idx
00: ed9e5b4179fc13fab1aa19beb933c0971742420fa3019c4d368d060d77e19e0e 342.672358737000 140640 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": 76403, "vin": [ { "gen": { "height": 76393 } } ], "vout": [ { "amount": 342672358737, "target": { "key": "ed9e5b4179fc13fab1aa19beb933c0971742420fa3019c4d368d060d77e19e0e" } } ], "extra": [ 1, 7, 175, 249, 14, 199, 194, 176, 203, 201, 130, 162, 25, 120, 4, 251, 132, 224, 144, 15, 219, 190, 50, 30, 108, 145, 178, 208, 140, 156, 247, 191, 123, 2, 17, 0, 0, 0, 61, 2, 107, 89, 243, 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