Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 957f084aa73f4aff4a04a1c70b9a86054ee1d75d77eab2cb2ea89ffbfee63c7a

Tx prefix hash: cfd3dbf223f7709820bcec0e3568469cb6947dbb22bd1e1f220fa403388a8bfd
Tx public key: afe3fb96778798c662491e7aae652e858806ecb17f0b8ccd8adc95f8209aff8b
Timestamp: 1761573471 Timestamp [UCT]: 2025-10-27 13:57:51 Age [y:d:h:m:s]: 00:057:14:29:32
Block: 1399111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41228 RingCT/type: yes/0
Extra: 01afe3fb96778798c662491e7aae652e858806ecb17f0b8ccd8adc95f8209aff8b02110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e97658831a13dc251cb0c766865cffe52da70dbceb87acf1708dbfaca60d50a8 0.600000000000 1887416 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": 1399121, "vin": [ { "gen": { "height": 1399111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e97658831a13dc251cb0c766865cffe52da70dbceb87acf1708dbfaca60d50a8" } } ], "extra": [ 1, 175, 227, 251, 150, 119, 135, 152, 198, 98, 73, 30, 122, 174, 101, 46, 133, 136, 6, 236, 177, 127, 11, 140, 205, 138, 220, 149, 248, 32, 154, 255, 139, 2, 17, 0, 0, 0, 4, 37, 163, 90, 15, 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