Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e7c36ac6b906040ad109b85e89bbf5da854bb00f874c43b1d8da7e831f3ef56

Tx prefix hash: 200ad73c5299345f926d7edc813b3bd2c0578a4fcb7b98dc47644f342104b299
Tx public key: ab1bc918eb1422e962edfd08530c93da0d84399b1281cd52aa56e615de1bf4e8
Timestamp: 1588514012 Timestamp [UCT]: 2020-05-03 13:53:32 Age [y:d:h:m:s]: 05:007:09:31:42
Block: 97918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181565 RingCT/type: yes/0
Extra: 01ab1bc918eb1422e962edfd08530c93da0d84399b1281cd52aa56e615de1bf4e80211000002ab86362411000000000000000000

1 output(s) for total of 290.775481304000 dcy

stealth address amount amount idx
00: c553f6f6cd05ec242414c0530422e5cc72238d497f0d13046c00960e766042f3 290.775481304000 173245 of 0

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": 97928, "vin": [ { "gen": { "height": 97918 } } ], "vout": [ { "amount": 290775481304, "target": { "key": "c553f6f6cd05ec242414c0530422e5cc72238d497f0d13046c00960e766042f3" } } ], "extra": [ 1, 171, 27, 201, 24, 235, 20, 34, 233, 98, 237, 253, 8, 83, 12, 147, 218, 13, 132, 57, 155, 18, 129, 205, 82, 170, 86, 230, 21, 222, 27, 244, 232, 2, 17, 0, 0, 2, 171, 134, 54, 36, 17, 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