Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae1a00f549ff9b01d41b6b0488962e088ff1466d768bd4cf9322b64dec4c4e58

Tx prefix hash: 6cce92c84f280a998a179c5badb1f5a19135da86c6b78d0f48ee7af9e89f2c70
Tx public key: bd2075a3a9f5afdc722cb7b24384bebf66e997432c6470e76c63c9be0da298a1
Timestamp: 1728691311 Timestamp [UCT]: 2024-10-12 00:01:51 Age [y:d:h:m:s]: 00:090:04:39:30
Block: 1129611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64460 RingCT/type: yes/0
Extra: 01bd2075a3a9f5afdc722cb7b24384bebf66e997432c6470e76c63c9be0da298a10211000000023cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4a3eb938f01886904c4ef7f1131489036c08ad07e2f565b5a84178bdb32c2b8 0.600000000000 1612442 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": 1129621, "vin": [ { "gen": { "height": 1129611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4a3eb938f01886904c4ef7f1131489036c08ad07e2f565b5a84178bdb32c2b8" } } ], "extra": [ 1, 189, 32, 117, 163, 169, 245, 175, 220, 114, 44, 183, 178, 67, 132, 190, 191, 102, 233, 151, 67, 44, 100, 112, 231, 108, 99, 201, 190, 13, 162, 152, 161, 2, 17, 0, 0, 0, 2, 60, 208, 252, 6, 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