Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 575d40554de96d28ca81c852784c116fb9bca9e4b0422c48ff0661f8fb761cd4

Tx prefix hash: 32ccb44f76c27c4aee28661975868535962e93a83edf0c5071fbfe4decf54ad4
Tx public key: fd2219b3ff351e3fb46706eaf87296e39b2b9a7bc445ef3c59a6c9cabe0e08c2
Timestamp: 1766714856 Timestamp [UCT]: 2025-12-26 02:07:36 Age [y:d:h:m:s]: 00:035:04:21:11
Block: 1441707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25013 RingCT/type: yes/0
Extra: 01fd2219b3ff351e3fb46706eaf87296e39b2b9a7bc445ef3c59a6c9cabe0e08c2021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ce183b8c1af8aa5d69c44b3b21452a112c4e991a8a31fdfd3344ea0a50d4ca4 0.600000000000 1930602 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": 1441717, "vin": [ { "gen": { "height": 1441707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ce183b8c1af8aa5d69c44b3b21452a112c4e991a8a31fdfd3344ea0a50d4ca4" } } ], "extra": [ 1, 253, 34, 25, 179, 255, 53, 30, 63, 180, 103, 6, 234, 248, 114, 150, 227, 155, 43, 154, 123, 196, 69, 239, 60, 89, 166, 201, 202, 190, 14, 8, 194, 2, 17, 0, 0, 0, 9, 214, 225, 157, 124, 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