Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 977153ea9775d6cf158e6eac4bc741aea0b608fe0b5244bb240d8265ec1e2235

Tx prefix hash: 91ab5eaba146a7d4af6067fe86ba0bdfd9032aee507f040da1d12939b95a2c91
Tx public key: 2535018b8b67c522978e1cdf5b43142313760ed70fb5f449d6db7d8460977f7c
Timestamp: 1714622866 Timestamp [UCT]: 2024-05-02 04:07:46 Age [y:d:h:m:s]: 00:342:03:08:43
Block: 1012982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244563 RingCT/type: yes/0
Extra: 012535018b8b67c522978e1cdf5b43142313760ed70fb5f449d6db7d8460977f7c0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6addd1d634bc8470c718aa69b3640ecabe1b5e917f719ca6fff5706840e8e6e8 0.600000000000 1475669 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": 1012992, "vin": [ { "gen": { "height": 1012982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6addd1d634bc8470c718aa69b3640ecabe1b5e917f719ca6fff5706840e8e6e8" } } ], "extra": [ 1, 37, 53, 1, 139, 139, 103, 197, 34, 151, 142, 28, 223, 91, 67, 20, 35, 19, 118, 14, 215, 15, 181, 244, 73, 214, 219, 125, 132, 96, 151, 127, 124, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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