Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14f29d37bdb504f50b2146e434560ed60e67fbf19934f4b1ac9db136ed2e3c29

Tx prefix hash: d7d73c1ec7f30484eafc287b1a8187f7968082d37e9575c0f1029e2d2ed27c8e
Tx public key: ffb34f4f83201c7a57aad5d38b8f3095774bcf100d50776e43637e46fab46265
Timestamp: 1755071592 Timestamp [UCT]: 2025-08-13 07:53:12 Age [y:d:h:m:s]: 00:092:04:32:52
Block: 1345924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65303 RingCT/type: yes/0
Extra: 01ffb34f4f83201c7a57aad5d38b8f3095774bcf100d50776e43637e46fab46265021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 408a7ec1519d198aa4f1f019958375c5b083f30addc535fa179039d2b6c2fff3 0.600000000000 1833821 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": 1345934, "vin": [ { "gen": { "height": 1345924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "408a7ec1519d198aa4f1f019958375c5b083f30addc535fa179039d2b6c2fff3" } } ], "extra": [ 1, 255, 179, 79, 79, 131, 32, 28, 122, 87, 170, 213, 211, 139, 143, 48, 149, 119, 75, 207, 16, 13, 80, 119, 110, 67, 99, 126, 70, 250, 180, 98, 101, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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