Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a75e1018ffd3444a3860d7d73130e7e59f32d11421d0757e05bce75d4d107b5a

Tx prefix hash: 9bd5b667baa4c59cc5605fe6e73d8dd7e62185246aba783d7f6ad06fc2d2c3a2
Tx public key: c6533327330c566a8d302d13ce6dcbcfd54c0125411734f8d25b45813bd856e8
Timestamp: 1733302962 Timestamp [UCT]: 2024-12-04 09:02:42 Age [y:d:h:m:s]: 00:117:14:05:07
Block: 1167740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83837 RingCT/type: yes/0
Extra: 01c6533327330c566a8d302d13ce6dcbcfd54c0125411734f8d25b45813bd856e8021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51837fd4ec657d74aca77d8a2be4120c148e5b4e37f4ed83d43d551aa1922752 0.600000000000 1653441 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": 1167750, "vin": [ { "gen": { "height": 1167740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51837fd4ec657d74aca77d8a2be4120c148e5b4e37f4ed83d43d551aa1922752" } } ], "extra": [ 1, 198, 83, 51, 39, 51, 12, 86, 106, 141, 48, 45, 19, 206, 109, 203, 207, 213, 76, 1, 37, 65, 23, 52, 248, 210, 91, 69, 129, 59, 216, 86, 232, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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