Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63abac716a048d3c847e9fc4d0f489d1643bf322122eb3bd014d884e923d48f5

Tx prefix hash: e7892f331b5d68ef3027efbc6b0739a803939cab77355cfa07a35df46c666424
Tx public key: 48946b131a011e2d668433e6bffde121ec30b7f4ac3b8962a1b878549011f193
Timestamp: 1578523287 Timestamp [UCT]: 2020-01-08 22:41:27 Age [y:d:h:m:s]: 04:324:05:10:27
Block: 41662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120911 RingCT/type: yes/0
Extra: 0148946b131a011e2d668433e6bffde121ec30b7f4ac3b8962a1b878549011f1930211000000022264afe6000000000000000000

1 output(s) for total of 446.649391952000 dcy

stealth address amount amount idx
00: 7e15e29e042606bb56c6be2f5e1fc811397b0e69bb8ba6d42673207ba8a0d3d1 446.649391952000 74416 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": 41672, "vin": [ { "gen": { "height": 41662 } } ], "vout": [ { "amount": 446649391952, "target": { "key": "7e15e29e042606bb56c6be2f5e1fc811397b0e69bb8ba6d42673207ba8a0d3d1" } } ], "extra": [ 1, 72, 148, 107, 19, 26, 1, 30, 45, 102, 132, 51, 230, 191, 253, 225, 33, 236, 48, 183, 244, 172, 59, 137, 98, 161, 184, 120, 84, 144, 17, 241, 147, 2, 17, 0, 0, 0, 2, 34, 100, 175, 230, 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