Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6da50cb7b4848e258a09002c3e406a2b5e554a616d8b12e6ec3c21623466f6ac

Tx prefix hash: 9d73ab68dba58d60b1f2283fc9e1532fc88b51d939947c259551c1e48c0e1e39
Tx public key: 5e610a83bc21df3d9d8a4ba3c4d74a1ded2fcfdb1168efc810919e2138d55bed
Timestamp: 1765741927 Timestamp [UCT]: 2025-12-14 19:52:07 Age [y:d:h:m:s]: 00:024:23:59:02
Block: 1433641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17916 RingCT/type: yes/0
Extra: 015e610a83bc21df3d9d8a4ba3c4d74a1ded2fcfdb1168efc810919e2138d55bed02110000000cd6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ef32a536f27840136f2264cc32a84ffb00012bc5363dd1ba070ee8262c7162d 0.600000000000 1922422 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": 1433651, "vin": [ { "gen": { "height": 1433641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ef32a536f27840136f2264cc32a84ffb00012bc5363dd1ba070ee8262c7162d" } } ], "extra": [ 1, 94, 97, 10, 131, 188, 33, 223, 61, 157, 138, 75, 163, 196, 215, 74, 29, 237, 47, 207, 219, 17, 104, 239, 200, 16, 145, 158, 33, 56, 213, 91, 237, 2, 17, 0, 0, 0, 12, 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