Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f942761075a39e98394f1f749b60f0d9a679bd576017358ff5d8a133064bdbfe

Tx prefix hash: f02019fe9ef40caf0005f0d213bef2a80e667bbce8c6012e299c2ded97d44415
Tx public key: 3b46a4ab0a6522ad370214d01134cf1cc0696e6efdf9792bfd8bddc95975b27d
Timestamp: 1696106260 Timestamp [UCT]: 2023-09-30 20:37:40 Age [y:d:h:m:s]: 01:237:07:31:25
Block: 859662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430704 RingCT/type: yes/0
Extra: 013b46a4ab0a6522ad370214d01134cf1cc0696e6efdf9792bfd8bddc95975b27d02110000000136a45730000000000000000000

1 output(s) for total of 0.870127659000 dcy

stealth address amount amount idx
00: a91afdef9c5bb8449684ab6b7deb23a522fbceaebacf4f78c04e2c7c134c6221 0.870127659000 1313900 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": 859672, "vin": [ { "gen": { "height": 859662 } } ], "vout": [ { "amount": 870127659, "target": { "key": "a91afdef9c5bb8449684ab6b7deb23a522fbceaebacf4f78c04e2c7c134c6221" } } ], "extra": [ 1, 59, 70, 164, 171, 10, 101, 34, 173, 55, 2, 20, 208, 17, 52, 207, 28, 192, 105, 110, 110, 253, 249, 121, 43, 253, 139, 221, 201, 89, 117, 178, 125, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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