Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8195ee80a24b123cc5eba7d242e1fbc6ed4706c8f44eafa8a67ae2321c4d95f8

Tx prefix hash: a8b6db5487bbd8eeb9c9293dc4e942efe7e4ec4f452cdd7c1fff485221868983
Tx public key: e5ce332f38caf62a52c2199589ee7e6d049176a9799beeb6aec27ed2d1f77268
Timestamp: 1718269345 Timestamp [UCT]: 2024-06-13 09:02:25 Age [y:d:h:m:s]: 00:297:04:20:57
Block: 1043212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212355 RingCT/type: yes/0
Extra: 01e5ce332f38caf62a52c2199589ee7e6d049176a9799beeb6aec27ed2d1f772680211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4e6d3f50e1898b1838919c873169afd13f52e90fd73c9b8f7733d40ac0ed07f 0.600000000000 1512309 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": 1043222, "vin": [ { "gen": { "height": 1043212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4e6d3f50e1898b1838919c873169afd13f52e90fd73c9b8f7733d40ac0ed07f" } } ], "extra": [ 1, 229, 206, 51, 47, 56, 202, 246, 42, 82, 194, 25, 149, 137, 238, 126, 109, 4, 145, 118, 169, 121, 155, 238, 182, 174, 194, 126, 210, 209, 247, 114, 104, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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