Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67a70e1a7ffb348509865bf87e991aa6922edb9c7c453b9db9e22dacc57775aa

Tx prefix hash: 40233d5133a85f5aa7effb1e5abe3f0ac122a93a3ebea7e25c5fd90bf8f87675
Tx public key: 6e5ef516c8da7c4a83445c526630bff73702e0bf0ab42257d7e007be2264bf11
Timestamp: 1765350803 Timestamp [UCT]: 2025-12-10 07:13:23 Age [y:d:h:m:s]: 00:013:11:16:47
Block: 1430399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9639 RingCT/type: yes/0
Extra: 016e5ef516c8da7c4a83445c526630bff73702e0bf0ab42257d7e007be2264bf11021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aeb54497bda78449cfda3e3e40e781c2096b2fa506382e4e79cb584e4983945c 0.600000000000 1919148 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": 1430409, "vin": [ { "gen": { "height": 1430399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aeb54497bda78449cfda3e3e40e781c2096b2fa506382e4e79cb584e4983945c" } } ], "extra": [ 1, 110, 94, 245, 22, 200, 218, 124, 74, 131, 68, 92, 82, 102, 48, 191, 247, 55, 2, 224, 191, 10, 180, 34, 87, 215, 224, 7, 190, 34, 100, 191, 17, 2, 17, 0, 0, 0, 9, 214, 225, 157, 124, 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