Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41a812bb56fe28b374ec0d293583882a91fc7726a56bceacbdd4eee7084d6533

Tx prefix hash: 7fcab109e12bd21513f6224fc8a477922b097d2d8a0988ae7a2982115eac82ad
Tx public key: 3df35d9ac24428b36b25ea9634a71db9bc3894d1f4f1c973a9061912b354c905
Timestamp: 1713209813 Timestamp [UCT]: 2024-04-15 19:36:53 Age [y:d:h:m:s]: 01:202:10:01:00
Block: 1001243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403335 RingCT/type: yes/0
Extra: 013df35d9ac24428b36b25ea9634a71db9bc3894d1f4f1c973a9061912b354c90502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: daaa2c0739c61a4bb2b479844983503ec8ff65a2c0a98de5c68b28a946820349 0.600000000000 1461747 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": 1001253, "vin": [ { "gen": { "height": 1001243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "daaa2c0739c61a4bb2b479844983503ec8ff65a2c0a98de5c68b28a946820349" } } ], "extra": [ 1, 61, 243, 93, 154, 194, 68, 40, 179, 107, 37, 234, 150, 52, 167, 29, 185, 188, 56, 148, 209, 244, 241, 201, 115, 169, 6, 25, 18, 179, 84, 201, 5, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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