Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be963f31be97a41cf7de2ede2f9d559928338d0ecc44e5ca1b806577a463ab9f

Tx prefix hash: 4ff3a13ae90f784f9493500b5fd83ff2344d7453074e207ffbc38c7c745515b9
Tx public key: 3c695979c21c1f4e3b62afa3cc8065f80d2bdd68a56470ad3fd1755b26ee15d5
Timestamp: 1758739343 Timestamp [UCT]: 2025-09-24 18:42:23 Age [y:d:h:m:s]: 00:090:08:57:39
Block: 1375611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64699 RingCT/type: yes/0
Extra: 013c695979c21c1f4e3b62afa3cc8065f80d2bdd68a56470ad3fd1755b26ee15d5021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45ee684e29f94b14d2a502a7b9897c9079b68de6c2f4eb5b773e1687b5638553 0.600000000000 1863702 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": 1375621, "vin": [ { "gen": { "height": 1375611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45ee684e29f94b14d2a502a7b9897c9079b68de6c2f4eb5b773e1687b5638553" } } ], "extra": [ 1, 60, 105, 89, 121, 194, 28, 31, 78, 59, 98, 175, 163, 204, 128, 101, 248, 13, 43, 221, 104, 165, 100, 112, 173, 63, 209, 117, 91, 38, 238, 21, 213, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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