Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d203eac91d853249ac1b982ddd4659489349ef0026ef3a5ba368e966bd78d8a

Tx prefix hash: d6be410422022ce94bb5171b894042e2d02bca535d9e675239743c275bc9cff2
Tx public key: 6b858ebb7c45ee72ae826f4d7b6c7126d0df0e49f93137e01e77a544c543c9a0
Timestamp: 1740263495 Timestamp [UCT]: 2025-02-22 22:31:35 Age [y:d:h:m:s]: 00:228:00:12:38
Block: 1225078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160671 RingCT/type: yes/0
Extra: 016b858ebb7c45ee72ae826f4d7b6c7126d0df0e49f93137e01e77a544c543c9a00211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b11c7f9c84a7136b801567e732255f97a7a54b596fdfa320828518b60cee0ea 0.600000000000 1711943 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": 1225088, "vin": [ { "gen": { "height": 1225078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b11c7f9c84a7136b801567e732255f97a7a54b596fdfa320828518b60cee0ea" } } ], "extra": [ 1, 107, 133, 142, 187, 124, 69, 238, 114, 174, 130, 111, 77, 123, 108, 113, 38, 208, 223, 14, 73, 249, 49, 55, 224, 30, 119, 165, 68, 197, 67, 201, 160, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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