Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ba667649e6b02cf07a8b36fb965fec104926468c64e8402a8b0d1529644ab33

Tx prefix hash: ec155e4ab1432dcbb4b6e5eb2701e44fc59b4e110f23c79952c7fe0369c476d9
Tx public key: f6b592af327fb7e4e2b2c320e812a6132dc7fa4bc4ebf70c3bfb60184597c0ec
Timestamp: 1698627470 Timestamp [UCT]: 2023-10-30 00:57:50 Age [y:d:h:m:s]: 01:079:11:13:51
Block: 880579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318007 RingCT/type: yes/0
Extra: 01f6b592af327fb7e4e2b2c320e812a6132dc7fa4bc4ebf70c3bfb60184597c0ec0211000000034b8f5122000000000000000000

1 output(s) for total of 0.741781912000 dcy

stealth address amount amount idx
00: c40e048effb201b799c83d8fb9d9cbbd8408c9f7732a909c9912a9e37f4eb3e5 0.741781912000 1336137 of 0

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": 880589, "vin": [ { "gen": { "height": 880579 } } ], "vout": [ { "amount": 741781912, "target": { "key": "c40e048effb201b799c83d8fb9d9cbbd8408c9f7732a909c9912a9e37f4eb3e5" } } ], "extra": [ 1, 246, 181, 146, 175, 50, 127, 183, 228, 226, 178, 195, 32, 232, 18, 166, 19, 45, 199, 250, 75, 196, 235, 247, 12, 59, 251, 96, 24, 69, 151, 192, 236, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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