Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a35d69659d607d0a9aacdf44b588dd2e3d6a15700615ec03d2b54fa1f0a884e

Tx prefix hash: 87d848e48044d5f0ba31881a51fbc103b0e1bc27564f0fcc7a7be87f20b6e4cc
Tx public key: 0ee9e9a0e3bb48ba1ec716e6ce1cfaf50c1c2aa7bbd85aed5121b645d7db2d85
Timestamp: 1715148228 Timestamp [UCT]: 2024-05-08 06:03:48 Age [y:d:h:m:s]: 00:233:11:48:52
Block: 1017338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167112 RingCT/type: yes/0
Extra: 010ee9e9a0e3bb48ba1ec716e6ce1cfaf50c1c2aa7bbd85aed5121b645d7db2d850211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5dec42e8d15b9388806f32c8c4982ed06d9e8b126a76680c649dfb7a3a3965b4 0.600000000000 1481113 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": 1017348, "vin": [ { "gen": { "height": 1017338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5dec42e8d15b9388806f32c8c4982ed06d9e8b126a76680c649dfb7a3a3965b4" } } ], "extra": [ 1, 14, 233, 233, 160, 227, 187, 72, 186, 30, 199, 22, 230, 206, 28, 250, 245, 12, 28, 42, 167, 187, 216, 90, 237, 81, 33, 182, 69, 215, 219, 45, 133, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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