Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf920cba13b34c0d4e3e934ea27d2242e3ea95f59fb7e26fff14440869c2d802

Tx prefix hash: 7fbb61cc84307a42c9a15e7f110d26367219e8cfb7fe81b594390baa7800848e
Tx public key: 1466586f26bb72db6610b39e3fea522dbefb7c7d2a1a017ee291ad96af66d92e
Timestamp: 1761218170 Timestamp [UCT]: 2025-10-23 11:16:10 Age [y:d:h:m:s]: 00:070:07:55:35
Block: 1396164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50347 RingCT/type: yes/0
Extra: 011466586f26bb72db6610b39e3fea522dbefb7c7d2a1a017ee291ad96af66d92e021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88bbe38fdfa49e9671a2e04e6f9dbdfb321d858930b8d4cc2987cea092e46102 0.600000000000 1884449 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": 1396174, "vin": [ { "gen": { "height": 1396164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88bbe38fdfa49e9671a2e04e6f9dbdfb321d858930b8d4cc2987cea092e46102" } } ], "extra": [ 1, 20, 102, 88, 111, 38, 187, 114, 219, 102, 16, 179, 158, 63, 234, 82, 45, 190, 251, 124, 125, 42, 26, 1, 126, 226, 145, 173, 150, 175, 102, 217, 46, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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