Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bfaa05d486c1eff01cc714cfe7bb07ff72751b66e798fdfd5343a84c118bc02

Tx prefix hash: ac360462f1105f8ea4c8420eb1cbb7a27a8b939fdbb3ceb77da1a9625f8f350a
Tx public key: a09ea0b992417817c559316828cae667a2e9c7e9f535b2d268938e7f19f73482
Timestamp: 1738855904 Timestamp [UCT]: 2025-02-06 15:31:44 Age [y:d:h:m:s]: 00:287:23:31:42
Block: 1213455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203565 RingCT/type: yes/0
Extra: 01a09ea0b992417817c559316828cae667a2e9c7e9f535b2d268938e7f19f734820211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 041f500244496eaf823df9c4615afda0b565cfcc45882f8afd40aeff9dee898b 0.600000000000 1700234 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": 1213465, "vin": [ { "gen": { "height": 1213455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "041f500244496eaf823df9c4615afda0b565cfcc45882f8afd40aeff9dee898b" } } ], "extra": [ 1, 160, 158, 160, 185, 146, 65, 120, 23, 197, 89, 49, 104, 40, 202, 230, 103, 162, 233, 199, 233, 245, 53, 178, 210, 104, 147, 142, 127, 25, 247, 52, 130, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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