Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c5fc174ba5523d18ba9650f7c77fdb48fe6cb94dcfac740b93f1d58826c356d

Tx prefix hash: 2fb08cf5ccac628e1a1e1623a1be9e58edecdcad855fc3c5b101a4a32ef0ed21
Tx public key: f21b21f0bf6a33de85fb904e7e39ea361c71c7c38589752b20067d8988ea6359
Timestamp: 1702786659 Timestamp [UCT]: 2023-12-17 04:17:39 Age [y:d:h:m:s]: 01:024:08:24:47
Block: 914845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278760 RingCT/type: yes/0
Extra: 01f21b21f0bf6a33de85fb904e7e39ea361c71c7c38589752b20067d8988ea6359021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be0e97b40103999ffd9a57abac058101d6fe4408fab2692db47dd73f8835a482 0.600000000000 1372197 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": 914855, "vin": [ { "gen": { "height": 914845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be0e97b40103999ffd9a57abac058101d6fe4408fab2692db47dd73f8835a482" } } ], "extra": [ 1, 242, 27, 33, 240, 191, 106, 51, 222, 133, 251, 144, 78, 126, 57, 234, 54, 28, 113, 199, 195, 133, 137, 117, 43, 32, 6, 125, 137, 136, 234, 99, 89, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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