Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7079e6af2de9d3a37475e05d9560e744c4fa184e4dc075f72c7765ac77f96d5e

Tx prefix hash: c237863eebf40c37b0767524a660b3e482a39968280c1ac640dca8c004c92f2e
Tx public key: 6ef0c64150cadfe39447d32f2ab20f4da4e90e857b9c90a9d731fb62d2b5afb2
Timestamp: 1763473027 Timestamp [UCT]: 2025-11-18 13:37:07 Age [y:d:h:m:s]: 00:009:20:25:15
Block: 1414838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7057 RingCT/type: yes/0
Extra: 016ef0c64150cadfe39447d32f2ab20f4da4e90e857b9c90a9d731fb62d2b5afb202110000000143b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cefba8d90ed225f5d3b6c302cd67547d283105080ced3ff41791a50a25365b7 0.600000000000 1903331 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": 1414848, "vin": [ { "gen": { "height": 1414838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cefba8d90ed225f5d3b6c302cd67547d283105080ced3ff41791a50a25365b7" } } ], "extra": [ 1, 110, 240, 198, 65, 80, 202, 223, 227, 148, 71, 211, 47, 42, 178, 15, 77, 164, 233, 14, 133, 123, 156, 144, 169, 215, 49, 251, 98, 210, 181, 175, 178, 2, 17, 0, 0, 0, 1, 67, 181, 4, 113, 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