Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be2fc1f8c0aecc97d912c5df3c7aff540d66561d239875b5e2b8d423232e03af

Tx prefix hash: 29a57351ac25cc4bedc46f6e8ce27a67aa1b1833dc337b4ff98c4000c964ca30
Tx public key: 09ca8b1e4016c37ff2208b52a5531ed64deca239c6e28ac35ff9ea3e59d8682d
Timestamp: 1750679957 Timestamp [UCT]: 2025-06-23 11:59:17 Age [y:d:h:m:s]: 00:150:16:05:47
Block: 1311126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105566 RingCT/type: yes/0
Extra: 0109ca8b1e4016c37ff2208b52a5531ed64deca239c6e28ac35ff9ea3e59d8682d02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a16bf4596862a23805ac235327235a89e3fd176b1deb29c9ab70dc0aacb8d19f 0.600000000000 1798751 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": 1311136, "vin": [ { "gen": { "height": 1311126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a16bf4596862a23805ac235327235a89e3fd176b1deb29c9ab70dc0aacb8d19f" } } ], "extra": [ 1, 9, 202, 139, 30, 64, 22, 195, 127, 242, 32, 139, 82, 165, 83, 30, 214, 77, 236, 162, 57, 198, 226, 138, 195, 95, 249, 234, 62, 89, 216, 104, 45, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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