Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cf3b01fd5b378772f5643bfedf468e13ad1f8f14049833bd7dc6cb4a1ec917a

Tx prefix hash: 089e7e6f71b6f2183cb42ff901e735a403d8a2c6120421eb32fe5ba834d9c81b
Tx public key: a67a43287bf01e8046e03ef83bb07528d4549a0a4888adfae305e65361b4443d
Timestamp: 1720975384 Timestamp [UCT]: 2024-07-14 16:43:04 Age [y:d:h:m:s]: 00:223:21:38:43
Block: 1065653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159896 RingCT/type: yes/0
Extra: 01a67a43287bf01e8046e03ef83bb07528d4549a0a4888adfae305e65361b4443d02110000001491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d95803811ecffa6704acf492d7f45eb67cb4e8e3b3c5a973bf9348abc2c02c3 0.600000000000 1536202 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": 1065663, "vin": [ { "gen": { "height": 1065653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d95803811ecffa6704acf492d7f45eb67cb4e8e3b3c5a973bf9348abc2c02c3" } } ], "extra": [ 1, 166, 122, 67, 40, 123, 240, 30, 128, 70, 224, 62, 248, 59, 176, 117, 40, 212, 84, 154, 10, 72, 136, 173, 250, 227, 5, 230, 83, 97, 180, 68, 61, 2, 17, 0, 0, 0, 20, 145, 225, 60, 4, 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