Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2dc755694fe33255f17dc4f9af512b06fd5f35c15bb39e026925d81471206d7f

Tx prefix hash: 8a0a4afe1275dbe589b89d684a713cbe2219f62894c6c7c9645692a0eff58598
Tx public key: 363fd9926cd3b3bbed87053e0560e9cdf621f4ba8bd015638a2fd532fd615b34
Timestamp: 1730087915 Timestamp [UCT]: 2024-10-28 03:58:35 Age [y:d:h:m:s]: 00:233:08:31:24
Block: 1141123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166534 RingCT/type: yes/0
Extra: 01363fd9926cd3b3bbed87053e0560e9cdf621f4ba8bd015638a2fd532fd615b340211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b39005e101eb662cae5585c0e737eafe625c42c8df1c62458d99038a5bd7d98f 0.600000000000 1624930 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": 1141133, "vin": [ { "gen": { "height": 1141123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b39005e101eb662cae5585c0e737eafe625c42c8df1c62458d99038a5bd7d98f" } } ], "extra": [ 1, 54, 63, 217, 146, 108, 211, 179, 187, 237, 135, 5, 62, 5, 96, 233, 205, 246, 33, 244, 186, 139, 208, 21, 99, 138, 47, 213, 50, 253, 97, 91, 52, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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