Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 839ec5933765b4f419635ddf873ca2776ceb0d254b14809712b7e102941fd2d3

Tx prefix hash: 28598d7e16d498ed635b1c5668cdb2b497239b4e65de1741f6bce8aa45934180
Tx public key: 8ba18421fdc91be605f1c78bcadf5c7a64b093e8b6040818dd1dda8494f29e00
Timestamp: 1713894904 Timestamp [UCT]: 2024-04-23 17:55:04 Age [y:d:h:m:s]: 00:262:00:42:43
Block: 1006945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187549 RingCT/type: yes/0
Extra: 018ba18421fdc91be605f1c78bcadf5c7a64b093e8b6040818dd1dda8494f29e0002110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ba82c75e5a25d993fee5b2ac3ae61cdd95aa03c6a951936c79f49cdbb31bb4b 0.600000000000 1468139 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": 1006955, "vin": [ { "gen": { "height": 1006945 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ba82c75e5a25d993fee5b2ac3ae61cdd95aa03c6a951936c79f49cdbb31bb4b" } } ], "extra": [ 1, 139, 161, 132, 33, 253, 201, 27, 230, 5, 241, 199, 139, 202, 223, 92, 122, 100, 176, 147, 232, 182, 4, 8, 24, 221, 29, 218, 132, 148, 242, 158, 0, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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