Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5ac77dcf85b0ae51cfd3bb6060ecc2f86217f3b64e090606bd3d8c96691aaa3

Tx prefix hash: d6c1dc685c3997073dae5f836f702a1b92a3c654111422d24449875a69f1ac7e
Tx public key: 25b5c976e92ce2b2a968938fbede90a38b4e1c4770f295d7f556ac8688736866
Timestamp: 1663255816 Timestamp [UCT]: 2022-09-15 15:30:16 Age [y:d:h:m:s]: 02:256:09:28:49
Block: 588543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 704591 RingCT/type: yes/0
Extra: 0125b5c976e92ce2b2a968938fbede90a38b4e1c4770f295d7f556ac8688736866021100000001ede25252000000000000000000

1 output(s) for total of 6.885140417000 dcy

stealth address amount amount idx
00: be4cddb99e843e7adf2f3f8f834da6a148ef22ef3270c6ea09191536c0d47daf 6.885140417000 1022768 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": 588553, "vin": [ { "gen": { "height": 588543 } } ], "vout": [ { "amount": 6885140417, "target": { "key": "be4cddb99e843e7adf2f3f8f834da6a148ef22ef3270c6ea09191536c0d47daf" } } ], "extra": [ 1, 37, 181, 201, 118, 233, 44, 226, 178, 169, 104, 147, 143, 190, 222, 144, 163, 139, 78, 28, 71, 112, 242, 149, 215, 245, 86, 172, 134, 136, 115, 104, 102, 2, 17, 0, 0, 0, 1, 237, 226, 82, 82, 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