Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f655783a9ef4b6449540b022a2d01ad6285560c24a3ce82005caec5e080e6b69

Tx prefix hash: d73a45ca1f380abdb5166aff2c146ee43ca357b72a94610279e60d1743d2ab6c
Tx public key: 749e3fdbd3742c9b438e019e2d127617971285e3582c2a9f1ab3c17c7e8786b5
Timestamp: 1755979867 Timestamp [UCT]: 2025-08-23 20:11:07 Age [y:d:h:m:s]: 00:042:04:40:12
Block: 1352921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30032 RingCT/type: yes/0
Extra: 01749e3fdbd3742c9b438e019e2d127617971285e3582c2a9f1ab3c17c7e8786b50211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4149e9f29502a5258d1ecc38ea8bc4818d03f6302081b968bb1e06eb881f213d 0.600000000000 1840890 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": 1352931, "vin": [ { "gen": { "height": 1352921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4149e9f29502a5258d1ecc38ea8bc4818d03f6302081b968bb1e06eb881f213d" } } ], "extra": [ 1, 116, 158, 63, 219, 211, 116, 44, 155, 67, 142, 1, 158, 45, 18, 118, 23, 151, 18, 133, 227, 88, 44, 42, 159, 26, 179, 193, 124, 126, 135, 134, 181, 2, 17, 0, 0, 0, 1, 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