Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fdc94a7a552a4d2edaf50f7bca6f6e727c7b7323ecbbd31aff86553129150cf

Tx prefix hash: 954410e32e2bafde18e05760ebd80cdf8022237146869fd050e89c622c4d41e2
Tx public key: f1fe3fd632e79e5d9aef39442f39a228661620a9eb30a296fa48db5b4bee0eae
Timestamp: 1708699643 Timestamp [UCT]: 2024-02-23 14:47:23 Age [y:d:h:m:s]: 01:063:04:23:06
Block: 963869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306201 RingCT/type: yes/0
Extra: 01f1fe3fd632e79e5d9aef39442f39a228661620a9eb30a296fa48db5b4bee0eae0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b7da0fae3dee1f62ac62fe32024a5648e1613c0df5c151c403ee80c211a3c4c 0.600000000000 1423596 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": 963879, "vin": [ { "gen": { "height": 963869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b7da0fae3dee1f62ac62fe32024a5648e1613c0df5c151c403ee80c211a3c4c" } } ], "extra": [ 1, 241, 254, 63, 214, 50, 231, 158, 93, 154, 239, 57, 68, 47, 57, 162, 40, 102, 22, 32, 169, 235, 48, 162, 150, 250, 72, 219, 91, 75, 238, 14, 174, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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