Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3f957bf374a67eff2f65fdbb4f6f8f71455f44bebf12b72a3eb94432df3534e

Tx prefix hash: 3886db101152cf77da4e1e7dceaf6ce66d7aca556a938e8ae89f2da2522f71d5
Tx public key: 0ca1282c7bce042244d9175f9195b9723f226e9c8d91f67d698c1b6798690064
Timestamp: 1703563054 Timestamp [UCT]: 2023-12-26 03:57:34 Age [y:d:h:m:s]: 01:318:18:59:03
Block: 921285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486673 RingCT/type: yes/0
Extra: 010ca1282c7bce042244d9175f9195b9723f226e9c8d91f67d698c1b6798690064021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a8002a88efb53d260d81c32b332874144ff508ab976f6a7e9835dd04924a4a1 0.600000000000 1378971 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": 921295, "vin": [ { "gen": { "height": 921285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a8002a88efb53d260d81c32b332874144ff508ab976f6a7e9835dd04924a4a1" } } ], "extra": [ 1, 12, 161, 40, 44, 123, 206, 4, 34, 68, 217, 23, 95, 145, 149, 185, 114, 63, 34, 110, 156, 141, 145, 246, 125, 105, 140, 27, 103, 152, 105, 0, 100, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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