Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 641a7196763a9ca140fae3de005166e8e26d69c8e774074502ef1ab0f9717d28

Tx prefix hash: da84d9da0684d68e3d02e4426b5933e8da8656d1dfa43d1f56d6d23583e6f56d
Tx public key: 8883299a6feb57ba8e39e3e457e4fe58e24c62903fc82c224451db92f10d7969
Timestamp: 1739963401 Timestamp [UCT]: 2025-02-19 11:10:01 Age [y:d:h:m:s]: 00:275:13:16:40
Block: 1222587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194720 RingCT/type: yes/0
Extra: 018883299a6feb57ba8e39e3e457e4fe58e24c62903fc82c224451db92f10d79690211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3745d01fc6c73ae4e631e42b608b7dd7398bc2edf18430b274a01bfa8d590312 0.600000000000 1709440 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": 1222597, "vin": [ { "gen": { "height": 1222587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3745d01fc6c73ae4e631e42b608b7dd7398bc2edf18430b274a01bfa8d590312" } } ], "extra": [ 1, 136, 131, 41, 154, 111, 235, 87, 186, 142, 57, 227, 228, 87, 228, 254, 88, 226, 76, 98, 144, 63, 200, 44, 34, 68, 81, 219, 146, 241, 13, 121, 105, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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