Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7e9b474be4b465a7ee7ca8f846c5b51a96d896e69cc675fc4ce8da37e70e117

Tx prefix hash: 956841c3c17aea6c5017bc37eaebdd52eb46d823b39ef7ac209709f9e0c06938
Tx public key: c071ee096b0657c05518ed3fda94750d5de175c53afbfda2b23b15eb1d1c3afb
Timestamp: 1765019442 Timestamp [UCT]: 2025-12-06 11:10:42 Age [y:d:h:m:s]: 00:028:23:36:12
Block: 1427647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20781 RingCT/type: yes/0
Extra: 01c071ee096b0657c05518ed3fda94750d5de175c53afbfda2b23b15eb1d1c3afb021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9856e3ddbd40399f3219c5a117cf98da7f6befb6fb91965953461f0281c6951 0.600000000000 1916350 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": 1427657, "vin": [ { "gen": { "height": 1427647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9856e3ddbd40399f3219c5a117cf98da7f6befb6fb91965953461f0281c6951" } } ], "extra": [ 1, 192, 113, 238, 9, 107, 6, 87, 192, 85, 24, 237, 63, 218, 148, 117, 13, 93, 225, 117, 197, 58, 251, 253, 162, 178, 59, 21, 235, 29, 28, 58, 251, 2, 17, 0, 0, 0, 3, 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