Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2af579967cf30a0d51c289570e4986086dfbedc41c0eaf43acea4b7c34d482c5

Tx prefix hash: df90650169fb7b344b4a50f127b8e884ab883a530640f494d7f40c72cab08043
Tx public key: dd1e84f8a7e0e756c223122d06193ef06621061687f6ac2d71f2b96a573aa3cf
Timestamp: 1765016809 Timestamp [UCT]: 2025-12-06 10:26:49 Age [y:d:h:m:s]: 00:057:04:40:32
Block: 1427629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40776 RingCT/type: yes/0
Extra: 01dd1e84f8a7e0e756c223122d06193ef06621061687f6ac2d71f2b96a573aa3cf02110000000143b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09bfd94eb776502ce9ee5ea4cac4307ab67a5cbc0e58e40be3131b0f6ecb6038 0.600000000000 1916332 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": 1427639, "vin": [ { "gen": { "height": 1427629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09bfd94eb776502ce9ee5ea4cac4307ab67a5cbc0e58e40be3131b0f6ecb6038" } } ], "extra": [ 1, 221, 30, 132, 248, 167, 224, 231, 86, 194, 35, 18, 45, 6, 25, 62, 240, 102, 33, 6, 22, 135, 246, 172, 45, 113, 242, 185, 106, 87, 58, 163, 207, 2, 17, 0, 0, 0, 1, 67, 181, 4, 113, 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