Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85f1b4afa25d2e3e2fc829c5255d90a9d192647d624d4412406a34bb62947bea

Tx prefix hash: 8c4021ef751899a9d7de2cccb675ac844f528ddf86f92511ef355ba99622bd96
Tx public key: 35b405c74f8889f56e2c3ebc1c3e7bd0dd8cf1dfcd94b03fdca4449501420fc4
Timestamp: 1716568610 Timestamp [UCT]: 2024-05-24 16:36:50 Age [y:d:h:m:s]: 00:310:19:13:50
Block: 1029111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222134 RingCT/type: yes/0
Extra: 0135b405c74f8889f56e2c3ebc1c3e7bd0dd8cf1dfcd94b03fdca4449501420fc40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 941d4815e4ffb0812db9489180a60b327f1e6608bde7a02896b38bdce0801655 0.600000000000 1497116 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": 1029121, "vin": [ { "gen": { "height": 1029111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "941d4815e4ffb0812db9489180a60b327f1e6608bde7a02896b38bdce0801655" } } ], "extra": [ 1, 53, 180, 5, 199, 79, 136, 137, 245, 110, 44, 62, 188, 28, 62, 123, 208, 221, 140, 241, 223, 205, 148, 176, 63, 220, 164, 68, 149, 1, 66, 15, 196, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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