Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14a64326cb09061ae0a7922a1d744bebe6ea5098f2f396f9d77abbe50e8b8df1

Tx prefix hash: 40a5971a6f6954568a1866cc376901728e12d667af792c274a939ad456df3f61
Tx public key: 40f5866e5190e8343c25aacea4824b797771d2c7b4a1218558a0256219bdb922
Timestamp: 1759061186 Timestamp [UCT]: 2025-09-28 12:06:26 Age [y:d:h:m:s]: 00:041:07:44:06
Block: 1378268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29596 RingCT/type: yes/0
Extra: 0140f5866e5190e8343c25aacea4824b797771d2c7b4a1218558a0256219bdb922021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 760e8a59d6a6607efb9d3fb30bd19fe66f630d78b81cb9c49cbf9c2205894519 0.600000000000 1866363 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": 1378278, "vin": [ { "gen": { "height": 1378268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "760e8a59d6a6607efb9d3fb30bd19fe66f630d78b81cb9c49cbf9c2205894519" } } ], "extra": [ 1, 64, 245, 134, 110, 81, 144, 232, 52, 60, 37, 170, 206, 164, 130, 75, 121, 119, 113, 210, 199, 180, 161, 33, 133, 88, 160, 37, 98, 25, 189, 185, 34, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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