Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fa38eb6fd8004e6ae69635d84e4e1b1cf70ac8c3f685bb74b4a2e7dfa925d38

Tx prefix hash: ba5d96fcaedae08fc8c2efc3b51993226a294d80efd0e8384e2f4c3253881295
Tx public key: 7223b4e5abc91bd1344ee284ee1bd9603140e06ab866cb219e28adb605489478
Timestamp: 1712325007 Timestamp [UCT]: 2024-04-05 13:50:07 Age [y:d:h:m:s]: 01:242:18:06:11
Block: 993897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432234 RingCT/type: yes/0
Extra: 017223b4e5abc91bd1344ee284ee1bd9603140e06ab866cb219e28adb60548947802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eabbc2dfcecc09ea40b5ea9b6cfcd22eb3c35f9dfb270f755aee70d7e9d1be23 0.600000000000 1454293 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": 993907, "vin": [ { "gen": { "height": 993897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eabbc2dfcecc09ea40b5ea9b6cfcd22eb3c35f9dfb270f755aee70d7e9d1be23" } } ], "extra": [ 1, 114, 35, 180, 229, 171, 201, 27, 209, 52, 78, 226, 132, 238, 27, 217, 96, 49, 64, 224, 106, 184, 102, 203, 33, 158, 40, 173, 182, 5, 72, 148, 120, 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