Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94325d66135c87dac84a5458c89e82bf8eb5782ea8cf284d4bf550cf2aead1d7

Tx prefix hash: dda8640969a8596b7f1b32d4643bb725ae441a7a043ce0d0c858d59429f4bd8e
Tx public key: 1c0150cd612e0c6c14c811278e9f2f73f7bff41485f8ac1372650145d088c5dc
Timestamp: 1734487837 Timestamp [UCT]: 2024-12-18 02:10:37 Age [y:d:h:m:s]: 00:018:04:17:24
Block: 1177581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12986 RingCT/type: yes/0
Extra: 011c0150cd612e0c6c14c811278e9f2f73f7bff41485f8ac1372650145d088c5dc0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d650a18a3dbf682a8baf38977e2b93b26a89f4dc464dd988faaba575bd44344 0.600000000000 1663952 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": 1177591, "vin": [ { "gen": { "height": 1177581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d650a18a3dbf682a8baf38977e2b93b26a89f4dc464dd988faaba575bd44344" } } ], "extra": [ 1, 28, 1, 80, 205, 97, 46, 12, 108, 20, 200, 17, 39, 142, 159, 47, 115, 247, 191, 244, 20, 133, 248, 172, 19, 114, 101, 1, 69, 208, 136, 197, 220, 2, 17, 0, 0, 0, 1, 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