Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e516fc0082571cda1f9c51fb758b5ef6a3798a8d385a54e979f95ed9ad5853d

Tx prefix hash: 2ca66b7ea772d549556150ac08df93f9db868b7d97e638ada1967a96d8eaa85e
Tx public key: 50002095a5a5bce87ee43c335e51eaf8303ee2831fae1c891bdc06a4da550e40
Timestamp: 1754513105 Timestamp [UCT]: 2025-08-06 20:45:05 Age [y:d:h:m:s]: 00:111:18:30:28
Block: 1341701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78916 RingCT/type: yes/0
Extra: 0150002095a5a5bce87ee43c335e51eaf8303ee2831fae1c891bdc06a4da550e400211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74cb95a9bbb467f8f24a4bfed24c6a53457bd824b53a1561e6abb2ccf5a4a1c0 0.600000000000 1829528 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": 1341711, "vin": [ { "gen": { "height": 1341701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74cb95a9bbb467f8f24a4bfed24c6a53457bd824b53a1561e6abb2ccf5a4a1c0" } } ], "extra": [ 1, 80, 0, 32, 149, 165, 165, 188, 232, 126, 228, 60, 51, 94, 81, 234, 248, 48, 62, 226, 131, 31, 174, 28, 137, 27, 220, 6, 164, 218, 85, 14, 64, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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