Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33f99397a55cb6d9b83abc52821161db5a28cf0bc42f4fd8cb11e11816a0b964

Tx prefix hash: 77e2b07d6becf2e0339e575956c7fa801560180e3ac90ab291cbf753877a109f
Tx public key: c97f8ae04f4a814795765fb63b28e5663019a8122da821d1390ba710a7009ee5
Timestamp: 1719395719 Timestamp [UCT]: 2024-06-26 09:55:19 Age [y:d:h:m:s]: 00:284:12:28:34
Block: 1052533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203302 RingCT/type: yes/0
Extra: 01c97f8ae04f4a814795765fb63b28e5663019a8122da821d1390ba710a7009ee502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcfc713d41c7a29faef815806eb2d444d03bf315cec405fc2d3dca67eaafec12 0.600000000000 1522862 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": 1052543, "vin": [ { "gen": { "height": 1052533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcfc713d41c7a29faef815806eb2d444d03bf315cec405fc2d3dca67eaafec12" } } ], "extra": [ 1, 201, 127, 138, 224, 79, 74, 129, 71, 149, 118, 95, 182, 59, 40, 229, 102, 48, 25, 168, 18, 45, 168, 33, 209, 57, 11, 167, 16, 167, 0, 158, 229, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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