Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea45fa973a40359092ac776548e67b36e1ff8a38976f8be0238b0926d67dcb5d

Tx prefix hash: 35a325ae8de475a3b36e80c0b5119207501cefc3e9b45b0b66b75617934bb47c
Tx public key: 0fe0993628e94ae3f1dca165cc685f2eb27ddba13167cc88b2d941a5d4319e7a
Timestamp: 1706690164 Timestamp [UCT]: 2024-01-31 08:36:04 Age [y:d:h:m:s]: 01:140:01:40:34
Block: 947190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361094 RingCT/type: yes/0
Extra: 010fe0993628e94ae3f1dca165cc685f2eb27ddba13167cc88b2d941a5d4319e7a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f729d200f23a9dbc72e7170c7bd468edcbf5a3e8efdc38b67db73e8b305ce6dd 0.600000000000 1405538 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": 947200, "vin": [ { "gen": { "height": 947190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f729d200f23a9dbc72e7170c7bd468edcbf5a3e8efdc38b67db73e8b305ce6dd" } } ], "extra": [ 1, 15, 224, 153, 54, 40, 233, 74, 227, 241, 220, 161, 101, 204, 104, 95, 46, 178, 125, 219, 161, 49, 103, 204, 136, 178, 217, 65, 165, 212, 49, 158, 122, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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