Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f1cf4ff00bbee95a13b3d55a7dd66c7fc799c2072deeb434d43bf9c7f4a5d6e

Tx prefix hash: 53ea75c327a49054dd78be60fbf262afe3e392d30ca8c8c97b46a77b23b95a68
Tx public key: 23118defae016f0c56781658a7cdd6e0772f003420254a340d5d0d4586baa6b9
Timestamp: 1719366509 Timestamp [UCT]: 2024-06-26 01:48:29 Age [y:d:h:m:s]: 00:327:06:37:43
Block: 1052288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233894 RingCT/type: yes/0
Extra: 0123118defae016f0c56781658a7cdd6e0772f003420254a340d5d0d4586baa6b90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 138616b584087cfc5729ae90ea8e1c6853c9167a07735c0433c5a9917f87ed9a 0.600000000000 1522611 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": 1052298, "vin": [ { "gen": { "height": 1052288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "138616b584087cfc5729ae90ea8e1c6853c9167a07735c0433c5a9917f87ed9a" } } ], "extra": [ 1, 35, 17, 141, 239, 174, 1, 111, 12, 86, 120, 22, 88, 167, 205, 214, 224, 119, 47, 0, 52, 32, 37, 74, 52, 13, 93, 13, 69, 134, 186, 166, 185, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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