Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bea4f9c1c8a4f8cfbb45300bc754efc90d6a2c2c9adac9de095d82477ca48bc3

Tx prefix hash: dfcc8dbcacb896013fa217f719e2a18cb1be56ef41495a0deb97f9d8fb7b43f3
Tx public key: f56c99d76a3293537ae8530648cc5d3632be0d1a220f8753ca2218a9448bfb96
Timestamp: 1582100251 Timestamp [UCT]: 2020-02-19 08:17:31 Age [y:d:h:m:s]: 05:056:13:34:46
Block: 67991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1193561 RingCT/type: yes/0
Extra: 01f56c99d76a3293537ae8530648cc5d3632be0d1a220f8753ca2218a9448bfb96021100000001c71d3ff9000000000000000000

1 output(s) for total of 365.357813217000 dcy

stealth address amount amount idx
00: ae2891a3df00f493dbcba95aa173cf823f04ce8941d459fc63902bff838335f4 365.357813217000 125247 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": 68001, "vin": [ { "gen": { "height": 67991 } } ], "vout": [ { "amount": 365357813217, "target": { "key": "ae2891a3df00f493dbcba95aa173cf823f04ce8941d459fc63902bff838335f4" } } ], "extra": [ 1, 245, 108, 153, 215, 106, 50, 147, 83, 122, 232, 83, 6, 72, 204, 93, 54, 50, 190, 13, 26, 34, 15, 135, 83, 202, 34, 24, 169, 68, 139, 251, 150, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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