Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa0e469182a40990c4244b8d869788c5da7f0ae9fd562aad06bf56176fac489e

Tx prefix hash: 5cf46c11fd0aaeef2efdf0cf53b58dbfc0cc5cb6f182b884195ec9b2bddd80ac
Tx public key: f614e72b2e282ae0f69b42d6914ae5b437187cf07035cdab9884f037d16feb09
Timestamp: 1713125792 Timestamp [UCT]: 2024-04-14 20:16:32 Age [y:d:h:m:s]: 00:316:15:44:22
Block: 1000544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226372 RingCT/type: yes/0
Extra: 01f614e72b2e282ae0f69b42d6914ae5b437187cf07035cdab9884f037d16feb0902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c346f99da25d967e83d4a884508e2af89d69ad747dc1b3cb7176af3fd82e6513 0.600000000000 1461042 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": 1000554, "vin": [ { "gen": { "height": 1000544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c346f99da25d967e83d4a884508e2af89d69ad747dc1b3cb7176af3fd82e6513" } } ], "extra": [ 1, 246, 20, 231, 43, 46, 40, 42, 224, 246, 155, 66, 214, 145, 74, 229, 180, 55, 24, 124, 240, 112, 53, 205, 171, 152, 132, 240, 55, 209, 111, 235, 9, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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