Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a0965b0ebb47e071b847012df2fc993256b66a084ec949fc3dae60120c1da1d

Tx prefix hash: ce500c490f2a4f074acfa700e8f126634f717c6d029a0ff0c39d96b39df2dc45
Tx public key: 350f76debd7c4807fb065ac64ae669c71d5f2c224cca9482704d7c213c3dae04
Timestamp: 1725947625 Timestamp [UCT]: 2024-09-10 05:53:45 Age [y:d:h:m:s]: 00:245:18:10:36
Block: 1106871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175498 RingCT/type: yes/0
Extra: 01350f76debd7c4807fb065ac64ae669c71d5f2c224cca9482704d7c213c3dae0402110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5fa169d3348b8808de560c661caad935add3ab86c14d3822d086a07ef16f17a 0.600000000000 1584472 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": 1106881, "vin": [ { "gen": { "height": 1106871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5fa169d3348b8808de560c661caad935add3ab86c14d3822d086a07ef16f17a" } } ], "extra": [ 1, 53, 15, 118, 222, 189, 124, 72, 7, 251, 6, 90, 198, 74, 230, 105, 199, 29, 95, 44, 34, 76, 202, 148, 130, 112, 77, 124, 33, 60, 61, 174, 4, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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