Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d74b015dc3a5af46825637dd89123a59b250db189480a2bc80a301e70217337c

Tx prefix hash: 53560cf32084e7066020d780c19a47bce41e8f1e5d1ef41a39cac034eb877efd
Tx public key: 7782e81457e720acc752250e2ad1d3bc4b4075be3d178a1e4dec52423f24a7f9
Timestamp: 1648206641 Timestamp [UCT]: 2022-03-25 11:10:41 Age [y:d:h:m:s]: 02:353:18:02:31
Block: 466034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 772153 RingCT/type: yes/0
Extra: 017782e81457e720acc752250e2ad1d3bc4b4075be3d178a1e4dec52423f24a7f902110000000fbf7ee4e7000000000000000000

1 output(s) for total of 17.532189387000 dcy

stealth address amount amount idx
00: 4a0f3608496c79c2a0e19424cd9c3d85eea85eb81d48c8f9d33dd2cd31ea8157 17.532189387000 884263 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": 466044, "vin": [ { "gen": { "height": 466034 } } ], "vout": [ { "amount": 17532189387, "target": { "key": "4a0f3608496c79c2a0e19424cd9c3d85eea85eb81d48c8f9d33dd2cd31ea8157" } } ], "extra": [ 1, 119, 130, 232, 20, 87, 231, 32, 172, 199, 82, 37, 14, 42, 209, 211, 188, 75, 64, 117, 190, 61, 23, 138, 30, 77, 236, 82, 66, 63, 36, 167, 249, 2, 17, 0, 0, 0, 15, 191, 126, 228, 231, 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