Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b7cd459267ddd9510086c533c1265d2051fcc1f3bb3afe44068f2a5d7f9e686

Tx prefix hash: 9d9b73ba5973731e9ce7c740bc4cd55a284d8db74005ed623816a9e98db44aab
Tx public key: d52375dc90cb88b5152b031f5975094808504de89fb77a46c902dc71a026ae87
Timestamp: 1709896987 Timestamp [UCT]: 2024-03-08 11:23:07 Age [y:d:h:m:s]: 01:099:22:43:56
Block: 973810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332353 RingCT/type: yes/0
Extra: 01d52375dc90cb88b5152b031f5975094808504de89fb77a46c902dc71a026ae8702110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a01a2258dc6f511b5f3977066e79c7e5af52311f1bca19904cdd00adc83bb0b 0.600000000000 1433749 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": 973820, "vin": [ { "gen": { "height": 973810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a01a2258dc6f511b5f3977066e79c7e5af52311f1bca19904cdd00adc83bb0b" } } ], "extra": [ 1, 213, 35, 117, 220, 144, 203, 136, 181, 21, 43, 3, 31, 89, 117, 9, 72, 8, 80, 77, 232, 159, 183, 122, 70, 201, 2, 220, 113, 160, 38, 174, 135, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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