Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4d54bf01b6f37d92f47c74bab456704dcedf4834d36f141cba8989c91749172

Tx prefix hash: 27f3d1f70b0eb159523b2e5b95aa0cda39f6bec0292f6c92e714382c7ad46073
Tx public key: dd2be8d628e9bf617980af67ccdf02ccefe4d3109fafd7e89693b3e10924727a
Timestamp: 1727420327 Timestamp [UCT]: 2024-09-27 06:58:47 Age [y:d:h:m:s]: 00:168:18:01:09
Block: 1119085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120415 RingCT/type: yes/0
Extra: 01dd2be8d628e9bf617980af67ccdf02ccefe4d3109fafd7e89693b3e10924727a021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c53acc241f39f0cce191a349e97f8ee660bd74d0f7bb219c2eb95b8a24e8eb2f 0.600000000000 1600510 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": 1119095, "vin": [ { "gen": { "height": 1119085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c53acc241f39f0cce191a349e97f8ee660bd74d0f7bb219c2eb95b8a24e8eb2f" } } ], "extra": [ 1, 221, 43, 232, 214, 40, 233, 191, 97, 121, 128, 175, 103, 204, 223, 2, 204, 239, 228, 211, 16, 159, 175, 215, 232, 150, 147, 179, 225, 9, 36, 114, 122, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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