Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb63242e2e9d9588d8259dd85fcf71302644702ab80199c3058b2f5e16dc0033

Tx prefix hash: f1c975e667aa57c35e962c99907c429bd4704bcaad28888fd42a6c42d9d6e643
Tx public key: 0c598679266750f8bdd694a589f1027fc04a65c97b75d4f5a6cca20aae5d43b9
Timestamp: 1718043435 Timestamp [UCT]: 2024-06-10 18:17:15 Age [y:d:h:m:s]: 00:142:17:02:59
Block: 1041338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102146 RingCT/type: yes/0
Extra: 010c598679266750f8bdd694a589f1027fc04a65c97b75d4f5a6cca20aae5d43b90211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 051d7c4e67b13b957c7422f09c4c00fafc90723fe84ec1f976f96a5ae48af48a 0.600000000000 1510003 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": 1041348, "vin": [ { "gen": { "height": 1041338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "051d7c4e67b13b957c7422f09c4c00fafc90723fe84ec1f976f96a5ae48af48a" } } ], "extra": [ 1, 12, 89, 134, 121, 38, 103, 80, 248, 189, 214, 148, 165, 137, 241, 2, 127, 192, 74, 101, 201, 123, 117, 212, 245, 166, 204, 162, 10, 174, 93, 67, 185, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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