Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97b3df6c755cb915a48d92addcbcff1b5e57672108efe0abfd460962057728f1

Tx prefix hash: f45054b412c2065a63cff561e48ed40b7183c91844363832dc46976cc72225d7
Tx public key: b1c3235e86483d5f175e1cefe8fde2fa8fab5c8676455b22dbb2a8178afbaa85
Timestamp: 1734632904 Timestamp [UCT]: 2024-12-19 18:28:24 Age [y:d:h:m:s]: 00:112:09:20:28
Block: 1178784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80090 RingCT/type: yes/0
Extra: 01b1c3235e86483d5f175e1cefe8fde2fa8fab5c8676455b22dbb2a8178afbaa85021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cabd71ab4d96cf1b71e8c96b8b50822eba8c0c76d4d1ae8d65fcadf738f353ed 0.600000000000 1665173 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": 1178794, "vin": [ { "gen": { "height": 1178784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cabd71ab4d96cf1b71e8c96b8b50822eba8c0c76d4d1ae8d65fcadf738f353ed" } } ], "extra": [ 1, 177, 195, 35, 94, 134, 72, 61, 95, 23, 94, 28, 239, 232, 253, 226, 250, 143, 171, 92, 134, 118, 69, 91, 34, 219, 178, 168, 23, 138, 251, 170, 133, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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