Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e290a23f5010de282ba0a1d5e5e8ed6c572600d8fba3be419cf715363c6aa75

Tx prefix hash: c16fbbe01e7b22b51718ffff2a71671a2d90cee5255f28f1959188317ce9bbb0
Tx public key: 1ba315af7f91e9d304b6dc40d4f09a132c196a282876c5702424f6dcb49916f5
Timestamp: 1714499469 Timestamp [UCT]: 2024-04-30 17:51:09 Age [y:d:h:m:s]: 01:161:12:48:54
Block: 1011962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374035 RingCT/type: yes/0
Extra: 011ba315af7f91e9d304b6dc40d4f09a132c196a282876c5702424f6dcb49916f502110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f556853c510ca1fcf9521f60de12038be5efdcc914e9aae7d3f41e0a4aea26bc 0.600000000000 1474332 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": 1011972, "vin": [ { "gen": { "height": 1011962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f556853c510ca1fcf9521f60de12038be5efdcc914e9aae7d3f41e0a4aea26bc" } } ], "extra": [ 1, 27, 163, 21, 175, 127, 145, 233, 211, 4, 182, 220, 64, 212, 240, 154, 19, 44, 25, 106, 40, 40, 118, 197, 112, 36, 36, 246, 220, 180, 153, 22, 245, 2, 17, 0, 0, 0, 5, 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