Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc483f512efead64121d50cd4ce9cb582c94a69bd2da2fc2318202cafe960a1b

Tx prefix hash: 8d84b86e942c4ecba7148280a74c5f2cc5fd5d09a1963adf239e0c61aa0b34f2
Tx public key: 40a2403e1eee9f052ce5632e8d195c900d1cf284d50a0b9daac93f7fb690c6b3
Timestamp: 1710782544 Timestamp [UCT]: 2024-03-18 17:22:24 Age [y:d:h:m:s]: 01:043:22:14:19
Block: 981160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292377 RingCT/type: yes/0
Extra: 0140a2403e1eee9f052ce5632e8d195c900d1cf284d50a0b9daac93f7fb690c6b302110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f8e700c6c567f411ef3f96817add2b2c47387ea644afc8c2ef7c2459e587eac 0.600000000000 1441253 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": 981170, "vin": [ { "gen": { "height": 981160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f8e700c6c567f411ef3f96817add2b2c47387ea644afc8c2ef7c2459e587eac" } } ], "extra": [ 1, 64, 162, 64, 62, 30, 238, 159, 5, 44, 229, 99, 46, 141, 25, 92, 144, 13, 28, 242, 132, 213, 10, 11, 157, 170, 201, 63, 127, 182, 144, 198, 179, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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