Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcd4265bf7cef4ea47dff32be7f2f57b6330458d5bd38caad57e9d5f563cb109

Tx prefix hash: a2e8e1205dd47298c911acf1b41fe9e6d4a809075b0f44e77f4a160d980cc63b
Tx public key: c9c4dfc6d6f8e8f36474c9ef839db4811e33ea5b05848a8163bf13d46aacf7a3
Timestamp: 1705865563 Timestamp [UCT]: 2024-01-21 19:32:43 Age [y:d:h:m:s]: 00:355:19:04:33
Block: 940346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254742 RingCT/type: yes/0
Extra: 01c9c4dfc6d6f8e8f36474c9ef839db4811e33ea5b05848a8163bf13d46aacf7a30211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc77ed10124310c64eda55eec24231f31239a86a2682fa86047a4d89a5ee4ec3 0.600000000000 1398482 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": 940356, "vin": [ { "gen": { "height": 940346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc77ed10124310c64eda55eec24231f31239a86a2682fa86047a4d89a5ee4ec3" } } ], "extra": [ 1, 201, 196, 223, 198, 214, 248, 232, 243, 100, 116, 201, 239, 131, 157, 180, 129, 30, 51, 234, 91, 5, 132, 138, 129, 99, 191, 19, 212, 106, 172, 247, 163, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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