Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b664209c961db6857ff522fdada1b1162a789b49c755335e3b322bf78b6cfbe

Tx prefix hash: 8dc84d48b2a6bf5b780c6fd1839a03e9e173e7f497807a98ad0ad191e248d142
Tx public key: 23329bcd257682c5119a85b5723232a5d7fa443c734cae685b3ee90976a4f78e
Timestamp: 1736404422 Timestamp [UCT]: 2025-01-09 06:33:42 Age [y:d:h:m:s]: 00:070:23:54:21
Block: 1193419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50528 RingCT/type: yes/0
Extra: 0123329bcd257682c5119a85b5723232a5d7fa443c734cae685b3ee90976a4f78e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa7c6d5ad7b1d80c13d0c825fcdd416deaa0504fc19e0217aeb561a74f0ea9e3 0.600000000000 1679980 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": 1193429, "vin": [ { "gen": { "height": 1193419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa7c6d5ad7b1d80c13d0c825fcdd416deaa0504fc19e0217aeb561a74f0ea9e3" } } ], "extra": [ 1, 35, 50, 155, 205, 37, 118, 130, 197, 17, 154, 133, 181, 114, 50, 50, 165, 215, 250, 68, 60, 115, 76, 174, 104, 91, 62, 233, 9, 118, 164, 247, 142, 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