Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe39aefb40b6b7a630cff6e32938f697d333966a72eeda1e040803c72325ccce

Tx prefix hash: 327e654ebfe24307db2cfd3b1f7a34cb711e616a9607c3fc9bf566aeb0684be0
Tx public key: 9ded34e8bac59aa979b5885f48ea319bce4b4862417d6d140b71ea902f651161
Timestamp: 1753269525 Timestamp [UCT]: 2025-07-23 11:18:45 Age [y:d:h:m:s]: 00:109:22:53:07
Block: 1331611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77399 RingCT/type: yes/0
Extra: 019ded34e8bac59aa979b5885f48ea319bce4b4862417d6d140b71ea902f651161021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adf41e5a47282d5f9b643db55b56a1f3c8a0b96d55573fbcb450b9e6767a7cbd 0.600000000000 1819406 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": 1331621, "vin": [ { "gen": { "height": 1331611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adf41e5a47282d5f9b643db55b56a1f3c8a0b96d55573fbcb450b9e6767a7cbd" } } ], "extra": [ 1, 157, 237, 52, 232, 186, 197, 154, 169, 121, 181, 136, 95, 72, 234, 49, 155, 206, 75, 72, 98, 65, 125, 109, 20, 11, 113, 234, 144, 47, 101, 17, 97, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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