Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64c5344358bc4a7821b779e44ca04884f00830cd8f92f0e2c9c0f2e0dafd5ea7

Tx prefix hash: 5f7535114517adca803e9f39c2a539d1788ba775c4bf5628e3cbaf9eac86a05e
Tx public key: 17ecd571ea30598a5b40fd89a28aa16ed5f4dbe84cbf1382b8cca10996c7ebd5
Timestamp: 1750818736 Timestamp [UCT]: 2025-06-25 02:32:16 Age [y:d:h:m:s]: 00:142:18:08:07
Block: 1312231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99962 RingCT/type: yes/0
Extra: 0117ecd571ea30598a5b40fd89a28aa16ed5f4dbe84cbf1382b8cca10996c7ebd5021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22639709c46a2f11f69a0e9e63ae2be2e65d132ec196e31ec6e2839ce6de1940 0.600000000000 1799862 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": 1312241, "vin": [ { "gen": { "height": 1312231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22639709c46a2f11f69a0e9e63ae2be2e65d132ec196e31ec6e2839ce6de1940" } } ], "extra": [ 1, 23, 236, 213, 113, 234, 48, 89, 138, 91, 64, 253, 137, 162, 138, 161, 110, 213, 244, 219, 232, 76, 191, 19, 130, 184, 204, 161, 9, 150, 199, 235, 213, 2, 17, 0, 0, 0, 1, 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